Everflow Outage History
Everflow is up right nowPingoru has recorded 25 incidents for Everflow: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 538 (0%) |
Incidents, newest first
Major February 3, 2026 Delayed Conversion Processing 2h 28m Conversion Processing
Started Feb 03, 2026, 03:40 PM UTC· resolved Feb 03, 2026, 06:09 PM UTC
- investigating Feb 03, 2026, 03:40 PM UTC
We are currently investigating an issue causing delays in conversion processing. Data is being captured, but reporting may lag behind real-time.
- monitoring Feb 03, 2026, 04:29 PM UTC
A fix has been implemented, and we are monitoring the system as processing returns to normal. We have begun backfilling any delayed conversions to ensure your reporting is 100% accurate. No data was lost during this incident.
- resolved Feb 03, 2026, 06:09 PM UTC
This incident has been resolved.
- postmortem Feb 03, 2026, 09:54 PM UTC
On February 3rd, starting at approximately 10:00 AM EST, a misconfiguration during a feature release impacted the processing speed of click ingestion. While clicks were being redirected at the usual speed, the process that allows for storing clicks and attributing conversions was delayed for roughly 90 minutes, until 11:30 AM EST. We have since isolated the conversions that were potentially dropped due to this delay. At 2:20 PM EST, we began "replaying" these events to ensure all data is accurately captured and recorded; this process is currently underway and is expected to be completed by 11:00 PM EST tonight. **What was not impacted:** Our endpoints for Clicks, Impressions, and Conversions continued to respond at standard speeds throughout the event. **What was possibly impacted:** Because of the processing delay, some Conversion, Payout, and Revenue caps may have exceeded their allowed limits. Additionally, the detection of tiered commission events may have been delayed in certain cases. **What was definitely impacted:** Customers utilizing our Firehose, as well as those using "New Conversion Registered" and "New Event Registered" notifications or webhooks, likely saw elevated error rates starting around 9:30 AM EST. During this window, some events may not have fired, or were delivered with missing properties. As these specific services \(Firehose and Webhooks\) cannot always be automatically replayed, we will be reviewing these instances on a case-by-case basis. If you have been affected by these specific service disruptions, please contact our support team so we can work with you to address your data needs.
Minor July 30, 2025 Geolocation Lookups Failing for a subset of traffic 3h
Started Jul 30, 2025, 04:00 PM UTC· resolved Jul 30, 2025, 07:00 PM UTC
- resolved Jul 30, 2025, 07:28 PM UTC
Geolocation lookup of clicks failed for a percentage of Everflow traffic over a period of 3 hours starting around noon EST The incident has now been resolved.
Major June 12, 2025 Unexpected System Disruption 1h 31m Everflow Web Application, Everflow API
Started Jun 12, 2025, 05:50 PM UTC· resolved Jun 12, 2025, 07:21 PM UTC
- investigating Jun 12, 2025, 06:29 PM UTC
We are investigating an issue that is affecting Everflow's systems. The underlying issues seems to come from the Google Cloud Platform. More details to come
- investigating Jun 12, 2025, 06:29 PM UTC
Google Cloud Platform, which Everflow is built on, experienced a major service outage which affected Everflow's platform : https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We are investigating the issue
- investigating Jun 12, 2025, 07:34 PM UTC
Google Cloud Platform, which Everflow is built on, experienced a major service outage which affected Everflow's platform : https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We are still monitoring our systems and investigating but all services are currently back online.
- resolved Jun 12, 2025, 07:44 PM UTC
This incident has been resolved.