Skip to main content

Is GIPHY Down?

No — GIPHY is up

We cannot measure GIPHY directly — it blocks automated checks — but GIPHY's own status page currently reports no issues.

Last checked · checks run every 6 hours

Official status page: https://status.giphy.com

Why there is no uptime figure on this page

The last time we fetched GIPHY's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether GIPHY works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and GIPHY's own status feed, which you can weigh yourself.

30-day history

Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: blocked from automated checks
Aug 1: blocked from automated checks
Aug 2: blocked from automated checks
Aug 3: blocked from automated checks
Aug 4: blocked from automated checks
Aug 5: blocked from automated checks
Aug 6: blocked from automated checks
Aug 7: blocked from automated checks
Aug 8: blocked from automated checks
Aug 9: blocked from automated checks
Aug 10: blocked from automated checks
Aug 11: blocked from automated checks
Aug 12: blocked from automated checks
Aug 13: blocked from automated checks
Aug 14: blocked from automated checks
Aug 15: blocked from automated checks
Aug 16: blocked from automated checks
Aug 17: blocked from automated checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
edge reachable

A static asset loaded in 6616ms. That proves the edge is up, but not that the site works.

arn
edge reachable

A static asset loaded in 6414ms. That proves the edge is up, but not that the site works.

bom
edge reachable

A static asset loaded in 7010ms. That proves the edge is up, but not that the site works.

cdg
edge reachable

A static asset loaded in 6168ms. That proves the edge is up, but not that the site works.

ord
edge reachable

A static asset loaded in 6204ms. That proves the edge is up, but not that the site works.

sin
edge reachable

A static asset loaded in 6776ms. That proves the edge is up, but not that the site works.

sjc
edge reachable

A static asset loaded in 6939ms. That proves the edge is up, but not that the site works.

syd
edge reachable

A static asset loaded in 6916ms. That proves the edge is up, but not that the site works.

yyz
edge reachable

A static asset loaded in 6494ms. That proves the edge is up, but not that the site works.

What GIPHY does

GIPHY hosts a searchable library of animated GIFs, clips and stickers, used both directly on giphy.com and through an API that other applications embed to power their own GIF pickers. That second role makes it a dependency for products that never mention it by name, which is why a GIPHY problem often surfaces inside a different app.

What an outage looks like

GIF search returns nothing or spins indefinitely, in a chat app rather than on GIPHY itself, which is how most people encounter it. Images resolve as broken thumbnails where a GIF should render, because the media host is separate from search. Uploads fail or hang partway. The GIPHY site can load normally while the API behind other apps is the part that is failing.

What to do about it

Check status.giphy.com, which separates the website components from the API, and tracks Search, Trending, Translate, Random and Upload individually, with Media listed apart from both. If a GIF picker inside another app is broken, the API components are the ones that matter, not the homepage. There is no recovery action to take beyond waiting, since nothing you send is lost.

Is it down for everyone, or just you?

If this page says GIPHY is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

GIPHY outage FAQ

Why is the GIF picker broken in another app?
Because many apps embed the GIPHY API rather than hosting their own library. When GIPHY's search or trending endpoints are degraded, the picker inside that app returns nothing, even though the app itself is perfectly healthy. This is the most common way a GIPHY outage is noticed, and it is why checking GIPHY is worth doing before reporting a bug to the other vendor.
Is the website down or just the API?
They are tracked separately, so either can fail alone. GIPHY lists the homepage, search and developer components under web and mobile, and lists the API endpoints on their own. giphy.com loading normally does not mean integrations are working, and a broken site does not necessarily mean the API is down. Check the specific component that matches how you use it.
Why do GIFs show as broken images rather than not loading at all?
Because delivery of the media files is a separate component from search. If search succeeds and media delivery is degraded, the app finds results and then fails to render them, which appears as broken thumbnails rather than an empty picker. The distinction is useful: broken images point at media delivery, an empty result set points at search.
Will an upload I started during an outage be lost?
An upload that failed did not complete, so the file stays on your device and can be re-uploaded once the service recovers. Upload is tracked as its own component and can fail while search works normally. Nothing already published to your GIPHY account is affected by an outage, and existing links resume working when media delivery returns.
Are GIFs already sent in a chat affected?
They can appear broken while the outage lasts, because most chat apps embed a link to the hosted file rather than copying it. The message itself is intact and the image returns once delivery recovers. Nothing needs re-sending, and re-sending during an incident only adds duplicates that will all render once the service is healthy again.

How we measure this

  • We request GIPHY's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where GIPHY publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when GIPHY blocks our checks entirely, we report the vendor's own status directly.

Get alerted when GIPHY goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required