Istoricul incidentelor Giphy

We are actively investigating an outage with Giphy API.

Our services are coming back on line. We are seeing 90% plus uptime across all our integrations. We will update here once we are at 100% uptime.

We are continuing to investigate this issue.

Giphy Website is down.

GIphy.com and Giphy API are back up.

This incident has been resolved.

Our teams are currently investigating the issue.

Our teams have resolved the incident.

We’re currently investigating an issue affecting the performance and/or availability of our search service. The team is actively working on mitigation

This incident has been resolved.

This incident has been resolved.

We’re currently investigating an issue affecting the performance and/or availability of our search service. The team is actively working on mitigation.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

There are elevated errors rates and increased latencies for several endpoints. We have identified the root cause and are working to restore full functionality.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating the issues.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have identified an issue with one of our downstream systems which is causing increased error rates on our API.

We are seeing signs of recovery and are actively monitoring.

Users may experience intermittent issues on our homepage (https://giphy.com). We have identified the issue and are will implement a fix shortly.

We have implemented a fix for issue that was affecting our Homepage. At this point all products are operational. We continue to monitor the situation.

This incident has been resolved.

Due to an ongoing incident surrounding our internal datastore update (see: scheduled maintenance), our Developer Portal (developer.giphy.com) is currently in a read-only state, as we monitor a fix that has been applied. During this time, you will not be able to create new applications, or modify/delete existing applications. No changes to the attributes of an API keys can be made during this period (e.g., upgrading a beta key to a production key). Note that the use of existing API keys by client applications will be unaffected. We will provide updates here, but expect this read-only operation to continue through this evening. Thank you for your patience, and we apologize for any inconvenience.

Thank you for your patience. We are happy to report our systems are fully operational, and developers may once again create new applications, or modify/delete existing ones. All the best!

We are aware that some users are experiencing SSL cert issues on our media urls. We are currently investigating and will update the status of this incident as we resolve this issue. Thank you for your patience.

Our SSL certificate has been updated and we verified that clients no longer reject it, specifically the firefox nightly browser.

We are experiencing issues with the GIPHY API and users may be experiencing 500 errors. We are working to resolve the issue.

The GIPHY API experienced an outage for about 25 minutes today from 3:20–3:45 ET. API clients may have experienced 500 errors for requests. We have resolved the issue and are monitoring closely. Please reach out to [email protected] with any questions.

The GIPHY for Chrome and GIPHY for Gmail extensions were compromised on Saturday June 17 between 11am–1pm ET when they were updated to include a malicious JavaScript file. We detected the issue and released an updated version of each extension immediately. The versions compromised are GIPHY for Chrome 1.4 and GIPHY for Gmail 1.5. The most up-to-date, safe versions are GIPHY for Chrome 1.5 and GIPHY for Gmail 1.6. Only users who updated their Chrome extensions during that window should be affected. We apologize for any inconvenience this may have caused. Please email [email protected] with any questions or concerns.

GIPHY API endpoints are experiencing issues related to S3 outage on Amazon Web Services including: problems serving uncached media assets, errors with sharing certain GIF renditions on social media, and upload errors. We are working hard to fix these issues while we wait for S3 to stabilize. Thank you for your patience!

We are still waiting for S3 to recover, and meanwhile, we are working to make sure all endpoints serving GIFs are stable, though we are still experiencing issues serving uncached media and errors on upload.

Now that S3 has stabilized, all issues with broken images or sharing GIFs should now be resolved. We are still seeing upload errors but will keep you posted as these resolve.

All GIPHY API endpoints are up and running: all features, media, and uploads should be working normally. You can now resume all of the searching, sharing, and creation of GIFs. Thank you for your patience today ❤️