outages.live
Live
AmplitudeIncident · 2026-10-13 18:53 UTC

Degraded Performance- Funnel charts renders as white text on a white/near-white background in light theme

ResolvedOfficial update

Since 2026-10-13 00:28 PT (07:28 UTC), we have identified an issue affecting Funnel charts in light theme where the conversion percentage data label displays as unreadable white text on a white background. This issue has been resolved as of 2026-10-13 01:24 PT (08:24 UTC). The conversion percentage data label on Funnel charts now displays correctly in light theme. The underlying data and calculations are not affected, and no data loss has occurred.

The latest update from Amplitude.

State

Resolved

Started

19 d ago

2026-10-13 18:53 UTC

Lasted

1 min

until 2026-10-13 18:53 UTC

Worst impact

Notice

Timeline

1 update
18:5318:5318:5318:5318:54
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Amplitude

Resolved2026-10-13 18:53 UTC

Since 2026-10-13 00:28 PT (07:28 UTC), we have identified an issue affecting Funnel charts in light theme where the conversion percentage data label displays as unreadable white text on a white background. This issue has been resolved as of 2026-10-13 01:24 PT (08:24 UTC). The conversion percentage data label on Funnel charts now displays correctly in light theme. The underlying data and calculations are not affected, and no data loss has occurred.

Affected components

2
Web ApplicationAnalytics - Web Application

Amplitude in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

21

Days with an incident

23

Median duration

1 h 15 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 5 min
median 1 h 15 min
90 days agoToday

Other Amplitude incidents

All incidents

Amplitude·Data Ingestion Delays

The issue has been fully resolved and data ingestion has returned to normal operation. No data was lost during this incident. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue.

Resolvedresolved 5 d ago

Amplitude·Delayed/Blocked Event Delivery to Amazon Kinesis Destination

This incident has been resolved. Event delivery to the Amazon Kinesis streaming destination has returned to normal operation. All affected events have been successfully delivered. We apologize for the disruption and appreciate your patience while we worked to resolve this issue.

Resolvedresolved 8 d ago

Amplitude·Streaming to External Destinations Unavailable

The issue has been fully resolved. Our Engineering team has implemented the necessary mitigation measures and functionality is now operational. We apologize for the disruption and appreciate your patience and understanding while we worked to restore service.

Resolvedresolved 9 d ago

Amplitude·Amplitude Website Outage

This incident has been resolved.

Resolvedresolved 9 d ago

Amplitude·Notice: Amplitude not impacted by recent PHP vulnerabilities

Amplitude has confirmed that no first-party Amplitude services are impacted by the PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (PHP2Shell Advisory). We are working with an affected third-party vendor to establish security updates on their end; however, internal hardening efforts should prevent potential escalation. No customer action is required at this time. As this is a developing advisory, any further updates will be communicated appropriately via our Trust Center at https://trust.amplitude.com/updates?tab=updates&update=65d46972-f7ed-4f53-bccf-f86f1d18393e. Please subscribe to our Trust Center for notification on updates as no further updates will be made on our Statuspage here.

Resolvedresolved 10 d ago

Follow Amplitude

Your coding agent knows when Amplitude is down, and tells you when a failure is theirs, not yours. You can also get Amplitude incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "amplitude" and tell me if Amplitude has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=amplitude
Slack
/feed subscribe https://outages.cc/feed.xml?providers=amplitude

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane