All Systems Operational

About This Site

Welcome to Amplitude's status page. To report a problem, please visit this page.

Uptime over the past 90 days. View historical uptime.
Analytics Operational
90 days ago
100.0 % uptime
Today
Web Reporting ? Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
Data Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
CLI/Codegen Operational
90 days ago
100.0 % uptime
Today
Data Processing Operational
Data Reception Operational
90 days ago
100.0 % uptime
Today
Cohort Export Operational
90 days ago
100.0 % uptime
Today
Event Streaming Operational
90 days ago
100.0 % uptime
Today
Data Export ? Operational
Experiment Operational
90 days ago
100.0 % uptime
Today
Evaluation API Operational
90 days ago
100.0 % uptime
Today
Management API Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
Flag Configurations API Operational
90 days ago
100.0 % uptime
Today
Web Experiment Script ? Operational
90 days ago
100.0 % uptime
Today
Audiences Operational
90 days ago
100.0 % uptime
Today
Profile API Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
Guides & Surveys Operational
90 days ago
100.0 % uptime
Today
Amazon Web Services Operational
Marketing Website Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 15, 2025

No incidents reported today.

Jun 14, 2025

No incidents reported.

Jun 13, 2025
Unexpected "[Segment]" Prefix in Event Types
Resolved - Amplitude has completed a data remediation plan to help impacted customers. The [Segment] prefix has been scrubbed from impacted events as of June 11, 2025. No action is required on your part. If you created an Amplitude event transformation as a short term fix to merge the incorrect event names, it is safe to remove those transformations now.
Jun 13, 11:42 PDT
Update - We've completed data cleanup for the majority of impacted customers and expect to finish cleanup for the remaining Amplitude organizations tomorrow. Your Amplitude Analytics charts and dashboards should now reflect the correct event names, with data from incorrectly named events successfully merged into the original event.

You may still see events with the [Segment] prefix in your schema or dropdowns; however, these no longer contain any associated data. We are continuing work to fully remove these incorrect event names from being visible in your Amplitude organization.

In parallel, we're continuing to look into downstream data remediation affecting Amplitude Activation and Data Warehouse destinations.

If your Analytics data still appears incorrect in charts or dashboards for the impacted time range (June 5, 2025, 11:00 UTC to 16:36 UTC), please submit a support ticket.

We'll keep you updated as we make further progress and will share another update tomorrow.
Jun 11, 06:21 PDT
Update - For customers who do not use Amplitude Activation or have a data warehouse connected to their Amplitude org, your impacted Segment data in Amplitude Analytics charts and dashboards should look as expected again. We are continuing to work on other downstream impact data remediation and will keep you updated on our progress. If your Amplitude Analytics data still does not look right for the impacted time range (June 5, 2025 11:00 UTC to June 5, 2025 16:36 UTC) please submit a support ticket.
Jun 9, 17:38 PDT
Update - We would like to provide an end-of-week update on the Segment incident. At this time, we are continuing to working on data remediation to help impacted customers. Our next step is to scrub the [Segment] prefix from impacted events, and we expect this to be fully completed by June 11, 2025. No action will be required on your part to resolve the incorrect event names in your Amplitude Analytics charts and dashboards. We will keep you updated on our progress.
Jun 6, 15:51 PDT
Update - We’ve finalized our remediation plan and are actively executing it. Our team is working to address the remaining impact and will continue to provide updates as progress is made.

Thank you for your patience.
Jun 5, 18:44 PDT
Update - Segment has deployed a fix to resolve an issue that impacted the Segment → Amplitude Actions destination integration from June 5th, 2025 11:00 UTC to 16:36 UTC.

During this time, events sent from Segment via the Actions destination were incorrectly prefixed with [Segment] (e.g., an event like Played Song became [Segment] Played Song). This caused incorrect event names to appear in Amplitude and may have disrupted downstream workflows or charts relying on existing event names.

This change did not affect customers using the legacy Classic Segment destination.

We’ve confirmed that no new events are arriving with the [Segment] prefix.

Amplitude is working on a data remediation plan to help impacted customers. Additional updates will be posted here as we finalize the cleanup options.

We sincerely apologize for the disruption and thank you for your patience.

Status: Monitoring
Impact: Segment Actions destination only (Classic unaffected)
Jun 5, 12:24 PDT
Monitoring - The fix has been deployed, and we are actively monitoring the situation.

We are currently evaluating options for data cleanup, which will take time to complete.
Jun 5, 10:01 PDT
Identified - We’ve identified the root cause and are actively working with the Segment team to implement a resolution. We will keep you informed as we make progress.
Jun 5, 09:25 PDT
Investigating - We wanted to inform you that we've identified an unexpected issue where a "[Segment]" prefix has been added to some event types starting earlier this morning.

Our team is actively investigating this and working closely with the Segment team to resolve the issue as quickly as possible. We understand the importance of consistent event naming for your workflows and analytics, and we're treating this with high priority.

We'll keep you updated as we make progress, and will notify you as soon as the issue is resolved. If you have any questions or need assistance in the meantime, feel free to reach out.

Thank you for your patience and understanding.
Jun 5, 09:01 PDT
Jun 12, 2025
Bigquery Export Failures
Resolved - Most GCP services fully recovered. Amplitude bigquery export has fully recovered as well.
Jun 12, 15:32 PDT
Monitoring - Monitoring GCP incidence for recovery
Jun 12, 12:18 PDT
Identified - Identified: Amplitude bigquery export is failing due to ongoing GCP incidence https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW starting from Jun/12 11:08AM PSP
Jun 12, 12:17 PDT
Jun 11, 2025
Data Processing Delays
Resolved - Data processing has fully recovered.

We’ve identified the root cause and implemented a fix.

Thank you for your patience.
Jun 11, 23:03 PDT
Monitoring - The downgrade component in the data processing system has recovered, and all lags have now cleared. We are continuing to monitor the system to ensure it remains fully stable.
Jun 11, 20:36 PDT
Update - We are continuing to investigate this issue.
Jun 11, 19:56 PDT
Investigating - Our data processing systems are delayed . This incident started at 18:40.

US customers will see delayed events.

We are investigating the issue and will post an update in an hour or earlier if we identify the issue.
Jun 11, 19:51 PDT
Data Processing Maintenance - US Data Center
Completed - The scheduled maintenance has been completed.
Jun 11, 10:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 11, 09:00 PDT
Scheduled - On June 11th, 16:00 UTC, we will be performing maintenance on components of the core ingestion infrastructure in our US data center.

During this time, customers may see slight data processing delays, and some temporary errors in the data collection endpoints could happen but are not expected. No data loss is expected during the maintenance.

The EU data center won't be affected.

We will post an update when the maintenance is completed.
Jun 9, 15:31 PDT
Jun 10, 2025

No incidents reported.

Jun 9, 2025
Jun 8, 2025

No incidents reported.

Jun 7, 2025

No incidents reported.

Jun 6, 2025
Jun 5, 2025
Jun 4, 2025

No incidents reported.

Jun 3, 2025

No incidents reported.

Jun 2, 2025

No incidents reported.

Jun 1, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage