Metrc outages and problems
User reports, last 24 hours
41 reports in total, counted in 15-minute windows
No problem reports came in for Metrc in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 41 reports. Most recent reports were about login (63%) and website (25%). The last spike in reports was 2 h ago and lasted 30 min. These are user reports from the US, where most people report Metrc problems.
- NormalClose to the usual level23 h 30 min · 17 reports
- ElevatedMore than 1.5 times the usual level15 min · 10 reports
- OutageMore than twice the usual level and far above the day's average15 min · 14 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 41 user reports came in for Metrc. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day.
The most recent spike big enough to count as an outage was 2 hours ago. The busiest 15-minute window of the day had 14 reports, about 2 hours ago.
-
Outage
Ended 2 h agoLasted 30 min14peak reports
Metrc in November 2026
- Problem reports in November (since 4 November)
- 41
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Metrc.
Share of 8 recent reports that said what was wrong.
Where Metrc problem reports come from
The map shows where recent problem reports for Metrc came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
Metrc problem spikes, last 30 days
Since 4 November, Metrc had 1 outage spike.
-
Outage
Thu 5 Nov, 12:58–13:28Lasted 30 min20peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 4 November 2026. Monthly reports for all services
How to fix Metrc not working
Metrc is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach metrc.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not Metrc.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as Metrc
Since 4 November, Metrc's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
Metrc: Thu 5 Nov, 12:58 to 13:28
- Facebook, outage,4 Nov 13:47 to 15:13
- Reddit, outage,4 Nov 21:13 to 15:13
- NTT Docomo, outage,03:28 to 15:13
- Odido, outage,03:28 to 15:13
- Klarmobil, outage,05:28 to 15:13
- State Bank of India (SBI), outage,06:28 to 14:43
- Community Fibre, outage,08:13 to 13:28
- SoftBank, outage,08:43 to 13:43
50 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
Metrc IP address, servers and network
- IPv4 addresses
- 104.18.30.106
Show all 2
- 104.18.31.106
- IPv6 addresses
- 2606:4700::6812:1e6a
Show all 2
- 2606:4700::6812:1f6a
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Cloudflare
- HTTPS certificate
- Issued by Sectigo Limited, valid until 21 Nov 2026 (15 days)
- HTTP/3
- Supported
- Our check
- Answered in 491 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, 1 h ago, for www.metrc.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from metrc.com. Fastest from Dallas (157 ms), slowest from Singapore (862 ms). Every location connected to the same address, on Microsoft Corporation (AS8075).
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 351 ms | 52.162.107.30 |
| ViennaAustria | Up · HTTP 301 | 387 ms | 52.162.107.30 |
| MilanItaly | Up · HTTP 301 | 352 ms | 52.162.107.30 |
| ParisFrance | Up · HTTP 301 | 377 ms | 52.162.107.30 |
| AmsterdamNetherlands | Up · HTTP 301 | 421 ms | 52.162.107.30 |
| MadridSpain | Up · HTTP 301 | 397 ms | 52.162.107.30 |
| WarsawPoland | Up · HTTP 301 | 393 ms | 52.162.107.30 |
| DallasUSA | Up · HTTP 301 | 157 ms | 52.162.107.30 |
| Los AngelesUSA | Up · HTTP 301 | 198 ms | 52.162.107.30 |
| São PauloBrazil | Up · HTTP 301 | 528 ms | 52.162.107.30 |
| SingaporeSingapore | Up · HTTP 301 | 862 ms | 52.162.107.30 |
| TokyoJapan | Up · HTTP 301 | 776 ms | 52.162.107.30 |
Checked with check-host.net from its servers in these cities 1 h ago, for metrc.com. Time is how long each server took to load the page.
Contact Metrc support
Tip: Metrc doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track Metrc
The status on this page comes from user-submitted problem reports for Metrc, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Metrc, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Metrc doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.