User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 9 min ago. Last stored result reached it in 167 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 07 | 0 | 0.0 | 163 ms | 0 |
| Mon 09 | 0 | 0.0 | 123 ms | 0 |
| Mon 12 | 0 | 0.0 | 162 ms | 0 |
| Mon 14 | 0 | 0.0 | 114 ms | 0 |
| Mon 16 | 0 | 0.0 | 257 ms | 0 |
| Mon 18 | 0 | 0.0 | 152 ms | 0 |
| Mon 20 | 0 | 0.0 | 286 ms | 0 |
| Mon 22 | 0 | 0.0 | 155 ms | 0 |
| Tue 00 | 0 | 0.0 | 194 ms | 0 |
| Tue 02 | 0 | 0.0 | 145 ms | 0 |
| Tue 04 | 0 | 0.0 | 154 ms | 0 |
| Tue 07 | 0 | 0.0 | 152 ms | 0 |
| Tue 09 | 0 | 0.0 | 261 ms | 0 |
| Tue 11 | 0 | 0.0 | 96 ms | 0 |
| Tue 13 | 0 | 0.0 | 195 ms | 0 |
| Tue 15 | 0 | 0.0 | 204 ms | 0 |
| Tue 17 | 0 | 0.0 | 162 ms | 0 |
| Tue 20 | 0 | 0.0 | 296 ms | 0 |
| Tue 22 | 0 | 0.0 | 218 ms | 0 |
| Wed 00 | 0 | 0.0 | 128 ms | 0 |
| Wed 02 | 0 | 0.0 | 211 ms | 0 |
| Wed 05 | 0 | 0.0 | 185 ms | 0 |
| Wed 07 | 0 | 0.0 | 136 ms | 0 |
| Wed 09 | 0 | 0.0 | 102 ms | 0 |
| Wed 12 | 0 | 0.0 | 118 ms | 0 |
| Wed 14 | 0 | 0.0 | 100 ms | 0 |
| Wed 16 | 0 | 0.0 | 167 ms | 0 |
| Wed 18 | 0 | 0.0 | 357 ms | 0 |
| Wed 20 | 0 | 0.0 | 133 ms | 0 |
| Wed 22 | 0 | 0.0 | 247 ms | 0 |
| Thu 01 | 0 | 0.0 | 249 ms | 0 |
| Thu 03 | 0 | 0.0 | 169 ms | 0 |
| Thu 05 | 0 | 0.0 | 243 ms | 0 |
| Thu 07 | 0 | 0.0 | 212 ms | 0 |
| Thu 09 | 0 | 0.0 | 128 ms | 0 |
| Thu 11 | 0 | 0.0 | 184 ms | 0 |
| Thu 13 | 0 | 0.0 | 272 ms | 0 |
| Thu 15 | 0 | 0.0 | 188 ms | 0 |
| Thu 17 | 0 | 0.0 | 192 ms | 0 |
| Thu 19 | 0 | 0.0 | 182 ms | 0 |
| Thu 21 | 0 | 0.0 | 150 ms | 0 |
| Thu 23 | 0 | 0.0 | 273 ms | 0 |
| Fri 00 | 0 | 0.0 | 121 ms | 0 |
| Fri 02 | 0 | 0.0 | 181 ms | 0 |
| Fri 04 | 0 | 0.0 | 171 ms | 0 |
| Fri 06 | 0 | 0.0 | 240 ms | 0 |
| Fri 08 | 0 | 0.0 | 167 ms | 0 |
| Fri 11 | 0 | 0.0 | 157 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for thirdweb yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when thirdweb goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send thirdweb alerts to Slack, Discord or a webhook — free.
We track thirdweb (thirdweb.com) as part of the Money group. Build on internet capital markets with infrastructure for agents to discover, pay for, and interact with services and APIs.
thirdweb publishes an official status page at status.thirdweb.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 191 ms average, 121–273 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public thirdweb incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
191 ms on average over the last 24 hours (121–273 ms).
Yes, at https://status.thirdweb.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report thirdweb here at once, the problem is on thirdweb's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with thirdweb. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.