User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Reforge down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → reforge.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 46 min ago. Last stored result reached it in 336 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 328 ms | 0 |
| Mon 16 | 0 | 0.0 | 375 ms | 0 |
| Mon 18 | 0 | 0.0 | 451 ms | 0 |
| Mon 20 | 0 | 0.0 | 210 ms | 0 |
| Mon 23 | 0 | 0.0 | 195 ms | 0 |
| Tue 01 | 0 | 0.0 | 293 ms | 0 |
| Tue 03 | 0 | 0.0 | 312 ms | 0 |
| Tue 05 | 0 | 0.0 | 499 ms | 0 |
| Tue 07 | 0 | 0.0 | 245 ms | 0 |
| Tue 09 | 0 | 0.0 | 358 ms | 0 |
| Tue 11 | 0 | 0.0 | 315 ms | 0 |
| Tue 14 | 0 | 0.0 | 475 ms | 0 |
| Tue 16 | 0 | 0.0 | 480 ms | 0 |
| Tue 18 | 0 | 0.0 | 234 ms | 0 |
| Tue 20 | 0 | 0.0 | 416 ms | 0 |
| Tue 23 | 0 | 0.0 | 353 ms | 0 |
| Wed 01 | 0 | 0.0 | 437 ms | 0 |
| Wed 03 | 0 | 0.0 | 459 ms | 0 |
| Wed 05 | 0 | 0.0 | 412 ms | 0 |
| Wed 07 | 0 | 0.0 | 298 ms | 0 |
| Wed 10 | 0 | 0.0 | 319 ms | 0 |
| Wed 12 | 0 | 0.0 | 212 ms | 0 |
| Wed 14 | 0 | 0.0 | 370 ms | 0 |
| Wed 16 | 0 | 0.0 | 496 ms | 0 |
| Wed 18 | 0 | 0.0 | 412 ms | 0 |
| Wed 21 | 0 | 0.0 | 437 ms | 0 |
| Wed 23 | 0 | 0.0 | 416 ms | 0 |
| Thu 01 | 0 | 0.0 | 479 ms | 0 |
| Thu 03 | 0 | 0.0 | 418 ms | 0 |
| Thu 05 | 0 | 0.0 | 318 ms | 0 |
| Thu 07 | 0 | 0.0 | 295 ms | 0 |
| Thu 09 | 0 | 0.0 | 232 ms | 0 |
| Thu 11 | 0 | 0.0 | 338 ms | 0 |
| Thu 13 | 0 | 0.0 | 408 ms | 0 |
| Thu 15 | 0 | 0.0 | 349 ms | 0 |
| Thu 17 | 0 | 0.0 | 214 ms | 0 |
| Thu 20 | 0 | 0.0 | 221 ms | 0 |
| Thu 22 | 0 | 0.0 | 246 ms | 0 |
| Fri 00 | 0 | 0.0 | 331 ms | 0 |
| Fri 02 | 0 | 0.0 | 371 ms | 0 |
| Fri 03 | 0 | 0.0 | 281 ms | 0 |
| Fri 05 | 0 | 0.0 | 320 ms | 0 |
| Fri 07 | 0 | 0.0 | 392 ms | 0 |
| Fri 09 | 0 | 0.0 | 319 ms | 0 |
| Fri 11 | 0 | 0.0 | 357 ms | 0 |
| Fri 13 | 0 | 0.0 | 318 ms | 0 |
| Fri 15 | 0 | 0.0 | 398 ms | 0 |
| Fri 17 | 0 | 0.0 | 336 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Reforge badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Reforge yet. Outages of 10 minutes or more get their own page here.
Having trouble with Reforge?
One report per service every 10 minutes from this network. No account.
Follow Reforge
Get an email when Reforge goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Reforge alerts to Slack, Discord or a webhook — free.
About Reforge
We track Reforge (reforge.com) as part of the Productivity group. Reforge connects you with insights from vetted operators that will drive impact for your team.
Reforge publishes an official status page at status.reforge.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 324 ms average, 221–398 ms range across 12 successful checks.
Questions
Is Reforge down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Reforge last down?
We have not recorded a public Reforge incident since monitoring began 8 days ago.
What is Reforge's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Reforge respond?
324 ms on average over the last 24 hours (221–398 ms).
Does Reforge have an official status page?
Yes, at https://status.reforge.com.
Reforge not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Reforge here at once, the problem is on Reforge'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 Reforge. 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.