User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
rconfig.com · Cloud & developer
Is rConfig 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 → rconfig.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 2 hr ago. Last stored result reached it in 382 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 22 | 0 | 0.0 | 79 ms | 0 |
| Tue 00 | 0 | 0.0 | 576 ms | 0 |
| Tue 02 | 0 | 0.0 | 184 ms | 0 |
| Tue 04 | 0 | 0.0 | 458 ms | 0 |
| Tue 06 | 0 | 0.0 | 64 ms | 0 |
| Tue 08 | 0 | 0.0 | 422 ms | 0 |
| Tue 10 | 0 | 0.0 | 427 ms | 0 |
| Tue 12 | 0 | 0.0 | 499 ms | 0 |
| Tue 14 | 0 | 0.0 | 469 ms | 0 |
| Tue 17 | 0 | 0.0 | 690 ms | 0 |
| Tue 19 | 0 | 0.0 | 116 ms | 0 |
| Tue 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 00 | 0 | 0.0 | 553 ms | 0 |
| Wed 02 | 0 | 0.0 | 135 ms | 0 |
| Wed 04 | 0 | 0.0 | 72 ms | 0 |
| Wed 06 | 0 | 0.0 | 68 ms | 0 |
| Wed 08 | 0 | 0.0 | 67 ms | 0 |
| Wed 11 | 0 | 0.0 | 117 ms | 0 |
| Wed 13 | 0 | 0.0 | 159 ms | 0 |
| Wed 15 | 0 | 0.0 | 523 ms | 0 |
| Wed 17 | 0 | 0.0 | 783 ms | 0 |
| Wed 19 | 0 | 0.0 | 754 ms | 0 |
| Wed 22 | 0 | 0.0 | 404 ms | 0 |
| Thu 00 | 0 | 0.0 | 489 ms | 0 |
| Thu 02 | 0 | 0.0 | 182 ms | 0 |
| Thu 04 | 0 | 0.0 | 1128 ms | 0 |
| Thu 06 | 0 | 0.0 | 146 ms | 0 |
| Thu 08 | 0 | 0.0 | 557 ms | 0 |
| Thu 10 | 0 | 0.0 | 488 ms | 0 |
| Thu 12 | 0 | 0.0 | 54 ms | 0 |
| Thu 14 | 0 | 0.0 | 747 ms | 0 |
| Thu 16 | 0 | 0.0 | 174 ms | 0 |
| Thu 18 | 0 | 0.0 | 911 ms | 0 |
| Thu 21 | 0 | 0.0 | 152 ms | 0 |
| Thu 23 | 0 | 0.0 | 99 ms | 0 |
| Fri 01 | 0 | 0.0 | 587 ms | 0 |
| Fri 02 | 0 | 0.0 | 147 ms | 0 |
| Fri 04 | 0 | 0.0 | 146 ms | 0 |
| Fri 06 | 0 | 0.0 | 813 ms | 0 |
| Fri 08 | 0 | 0.0 | 135 ms | 0 |
| Fri 10 | 0 | 0.0 | 92 ms | 0 |
| Fri 11 | 0 | 0.0 | 730 ms | 0 |
| Fri 12 | 0 | 0.0 | 98 ms | 0 |
| Fri 14 | 0 | 0.0 | 93 ms | 0 |
| Fri 16 | 0 | 0.0 | 964 ms | 0 |
| Fri 18 | 0 | 0.0 | 889 ms | 0 |
| Fri 20 | 0 | 0.0 | 887 ms | 0 |
| Fri 21 | 0 | 0.0 | 382 ms | 0 |
Reliability
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live rConfig 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 rConfig yet. Outages of 10 minutes or more get their own page here.
Having trouble with rConfig?
One report per service every 10 minutes from this network. No account.
Follow rConfig
Get an email when rConfig goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send rConfig alerts to Slack, Discord or a webhook — free.
About rConfig
rConfig, at rconfig.com, is one of the Cloud & developer services we monitor. Enterprise network configuration management for multi-vendor backups, compliance, and automation. Get visibility, rollback, and audit-ready change history.
rConfig publishes an official status page at status.rconfig.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 459 ms average, 92–964 ms range across 13 successful checks.
Questions
Is rConfig down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was rConfig last down?
We have not recorded a public rConfig incident since monitoring began 7 days ago.
What is rConfig's uptime?
From our own checks: 100% over 7 days of checks.
How fast does rConfig respond?
459 ms on average over the last 24 hours (92–964 ms).
Does rConfig have an official status page?
Yes, at https://status.rconfig.com.
rConfig 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report rConfig here at once, the problem is on rConfig'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 rConfig. 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.