Everflow 中断历史

We are currently investigating an issue causing delays in conversion processing. Data is being captured, but reporting may lag behind real-time.

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.

This incident has been resolved.

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.

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.

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

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

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.

This incident has been resolved.

We are investigating an issue that happened with impressions, clicks and conversions. The issue affects a portion of our clients.

This incident has been resolved.

The issue has been identified and we are working with our service provider to remediate the issue.

This incident has been resolved.

Incident Status: Resolved Date: March 15, 2024 Time: 3:10 PM UTC - 7:10 PM UTC Issue: We experienced an issue with our email delivery system, causing delays and failures in sending and receiving emails for some users. Impact: - Delayed email delivery - Failed email delivery attempts

Please note that we are currently investigating an email delivery issue and are working with our email provider to resolve this issue.

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

This incident has been resolved.

We experienced tracking issues with our Javascript SDK, which has since been corrected. Started between 8:18pm UTC - 8:40pm UTC Resolved between 9:38pm UTC - 9:44pm UTC

We are investigating an issue that happened with impressions, clicks and conversions. Timeline: - Our monitoring identified an issue with incoming traffic, starting around 10:02am EDT - We quickly resolved the issue with the faulty service and traffic was resumed around 10:12am EDT - All missing conversions were reprocessed and added back to the system as of 2:50pm EDT ----- If you have any questions about this incident, you can reach out to our support team, [email protected] Everflow Team

We are currently investigating a cloud-provider networking issue affecting all Everflow services.

We are continuing to investigate this issue.

This incident has been resolved. Please note this incident was related to a networking issue within Google Cloud (refer to https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh for more details)

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating an incident where our Web application and API are not reachable for a majority of our clients

The issue has been identified and a fix is being implemented.

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

This incident has been resolved.

To answer the incidents we had on October 2nd, the Everflow team is jointly working with the Google Cloud team to deploy a long term fix. During the maintenance, the API and the application will be down but there won't be any impact on clicks / impressions. The conversions will be buffered and processed again after the maintenance

We are investigating an ongoing global system issue

The incident has been resolved.

The issue has been identified and we are working on it

We are continuing to work on a fix for this issue.

We have started processing traffic again, monitoring performance and stability

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We identified and fixed an issue that caused a partial system disruption of our services between 6:15am UTC and 6:30am UTC. During that period, the API was partially available and a small number of conversions were rejected by our system. The impact was minimal on impressions and clicks. We apologize for any inconvenience caused by these incidents and rest assured we will be investigating to make sure these don't happen again. Please contact our support team @ https://help.everflow.io/ if you have any specific questions regarding these incidents. Everflow Team

The issue has been identified and a fix is on the way.

A fix has been implemented and we are monitoring the results

This incident has been resolved

Google Cloud Power Outage Following a power outage inside one of Google Cloud datacenter, the Everflow platform was down between 12:55pm UTC and 4:20pm UTC. During that time, all Everflow services were impacted. We apologize for any inconvenience caused by these incidents and rest assured we will be investigating to make sure these don't happen again. Please contact our support team @ https://help.everflow.io/ if you have any specific questions regarding these incidents. *UPDATE* Google released a post-mortem regarding the outage they occurred on June 29th 2020 in their us-east1 region: https://status.cloud.google.com/incident/cloud-networking/20005

We identified and fixed an issue that caused most of our services to be down between 4:11pm UTC and 4:18pm UTC. During that period, the API was not accessible and most of the conversions were rejected by our system. The impact was minimal on impressions and clicks. We apologize for any inconvenience caused by these incidents and rest assured we will be investigating to make sure these don't happen again. Please contact our support team @ https://help.everflow.io/ if you have any specific questions regarding these incidents. Everflow Team