- Service Status
- /
- GIPHY
Is GIPHY Down?
- GIPHY's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 247 ms
Right now
The verdict is the worse of these two. How we decide
GIPHY's status page
status.giphy.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Homepage | Operational |
| Search | Operational |
| Developers | Operational |
| Media | Operational |
| Search | Operational |
| Trending | Operational |
| Translate | Operational |
| Random | Operational |
| Upload | Operational |
FlareWarden checks
giphy.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 247 ms
- Checked
By region
- Amsterdam reachable, 205 ms
- Chicago reachable, 142 ms
- Paris reachable, 184 ms
- San Jose reachable, 241 ms
- Singapore reachable, 382 ms
- Stockholm reachable, 218 ms
- Sydney reachable, 410 ms
- Toronto reachable, 201 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 36 ms | 3 ms | 7 ms | 193 ms |
| Chicago | 27 ms | 1 ms | 4 ms | 130 ms |
| Paris | 28 ms | 1 ms | 9 ms | 177 ms |
| San Jose | 77 ms | 1 ms | 5 ms | 231 ms |
| Singapore | 7 ms | 1 ms | 4 ms | 309 ms |
| Stockholm | 51 ms | 0 ms | 5 ms | 204 ms |
| Sydney | 142 ms | 1 ms | 4 ms | 403 ms |
| Toronto | 102 ms | 0 ms | 7 ms | 191 ms |
History
Incidents GIPHY reported
Since Oct 22, 3 days · from status.giphy.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
GIPHY website availability
Measured by FlareWarden · giphy.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 339ms
Last 30 days
68-day clean streakMeasured by FlareWarden's own checks of giphy.com from multiple regions every 6 hours. GIPHY's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 68 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 up to 17 cities across three regions to find out where it breaks.
Related services
GIPHY outage FAQ
Why is the GIF picker broken in another app?
Is the website down or just the API?
Why do GIFs show as broken images rather than not loading at all?
Will an upload I started during an outage be lost?
Are GIFs already sent in a chat affected?
How we measure this
- We request GIPHY's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of GIPHY itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when GIPHY goes down
We check GIPHY every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring
