Amplitude service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for amplitude.com. Compare the regional responses with the problem you see in Amplitude.
Find Amplitude help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Event ingestion, dashboard queries and account access are separate. A marketing-site response says little about whether analytics events arrived.
The checker above requests amplitude.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Amplitude action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Include the Amplitude project and ingestion or query context.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
Open Amplitude help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Project identifier, event name, event time, SDK version and ingestion/request error; redact user data and API secrets.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Amplitude.
These are troubleshooting comparisons, not claims that Amplitude is currently experiencing a particular incident.
Compare the affected chart with another chart over the same time range and confirm the selected project.
For missing events, inspect a single test event's delivery and ingestion response before replaying a backlog.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Amplitude seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open amplitude.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Amplitude issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Amplitude support.
Run the amplitude.com check and compare its original timestamps and responses with your actual error. Event ingestion, dashboard queries and account access are separate. A marketing-site response says little about whether analytics events arrived.
Use the official help/reporting resource linked above. Include the Amplitude project and ingestion or query context.
Compare the affected chart with another chart over the same time range and confirm the selected project. For missing events, inspect a single test event's delivery and ingestion response before replaying a backlog.
Project identifier, event name, event time, SDK version and ingestion/request error; redact user data and API secrets.