outages.live
Live
DiscordIncident · 2026-09-16 16:15 UTC

Google Pay Outage

ResolvedOfficial update

This incident has been resolved.

The latest update from Discord.

State

Resolved

Started

46 d ago

2026-09-16 16:15 UTC

Lasted

28 min

until 2026-09-16 16:43 UTC

Worst impact

Partial outage

Timeline

2 updates
16:1516:2216:2916:3616:43
Partial outageUpdate postedTimes in UTC

Identified

28 min 100%

Updates

Times in UTC

As posted by Discord

Resolved2026-09-16 16:43 UTC

This incident has been resolved.

Identified2026-09-16 16:15 UTC

We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play. Purchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active. We're monitoring Google's status and will post an update as soon as service is restored. No action is needed on your part — please try again later. https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav

Discord in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

15

Median duration

1 h 2 min

This incident

55% shorter than the median

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

6 h 17 min
median 1 h 2 min
90 days agoToday

Other Discord incidents

All incidents

Discord·Issues establishing voice call

This incident has been resolved.

Resolvedresolved 11 h ago

Discord·Issues establishing voice calls

This incident has been resolved.

Resolvedresolved 2 d ago

Discord·Elevated API error rate

This incident has been resolved.

Resolvedresolved 30 d ago

Discord·Age group status mismatch across devices

This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20

Resolvedresolved 38 d ago

Discord·Issue / Delay in establishing call connection

This incident has been resolved.

Resolvedresolved 45 d ago

Follow Discord

Your coding agent knows when Discord is down, and tells you when a failure is theirs, not yours. You can also get Discord 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 "discord" and tell me if Discord 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=discord
Slack
/feed subscribe https://outages.cc/feed.xml?providers=discord

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane