Is MetaMask down?
Awaiting datachecked 9 minutes ago
Our checks of MetaMask pass from 0 of the 4 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.
As of Nov 5, 2026, 2:51 PM UTC, RealUptime's checks of MetaMask passed in all 4 regions that returned a reading.
Our checks of MetaMask did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show MetaMask works for users.
MetaMask publishes no status feed we can read, so the only reading here is our check reading on the left.
MetaMask response time, by region
No response-time data yet for US-East.
No response-time data yet for US-West.
No response-time data yet for Europe.
No response-time data yet for Asia-Pacific.
Check your own site while you wait on MetaMask
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not MetaMask. It cannot diagnose MetaMask's own systems.
What we measured, function by function
MetaMask answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
- APIprimaryUS-East: Awaiting dataUS-West: Awaiting dataEurope: Awaiting dataAsia-Pacific: Awaiting dataUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
Get an email when our checks of MetaMask fail from two or more distant regions, and again when they pass
Get an email when our checks change
We will email you when our checks of MetaMask fail from two or more distant regions, and again when they pass. No account, no card.
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1270msstatus code: 200checked: Nov 5, 2026, 2:51 PM UTC0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for MetaMask from US-East, and not enough reports from there to say anything on their own.
- US-WestChecks passinglatency: 2034msstatus code: 200checked: Nov 5, 2026, 2:50 PM UTC0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for MetaMask from US-West, and not enough reports from there to say anything on their own.
- US-CentralNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeChecks passinglatency: 1315msstatus code: 200checked: Nov 5, 2026, 2:50 PM UTC0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for MetaMask from Europe, and not enough reports from there to say anything on their own.
- UKNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 2227msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for MetaMask from Asia-Pacific, and not enough reports from there to say anything on their own.
- Southeast AsiaNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionMetaMask is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using MetaMask, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for MetaMask yet, which is not evidence that nothing is wrong.
Recent probe events
No probe events on record yet for MetaMask.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring MetaMask since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for MetaMask covering any window you pick, with our check readings and MetaMask's own claim at the time, side by side.
Full check history for MetaMask: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/metamask)<a href="https://realuptime.io/outages/metamask"><img src="https://realuptime.io/outages/metamask/badge.svg?days=30" alt="MetaMask uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is MetaMask down?", https://realuptime.io/outages/metamask. The readings change with every check, so give the date you read them.
How our checks compare with MetaMask's stated SLA
At or above your target
Our checks of MetaMask failed for none over the 72h 45m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from MetaMask's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means the service returned real data from its own backend, with the content we expect. It does not show that every feature, account type or region works, or that sign-in is healthy.
Host checked: token-api.metaswap.codefi.network