User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Social
Is Saddleback Communications 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 → saddlebackcomm.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 57 min ago. Last stored result reached it in 131 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 252 ms | 0 |
| Tue 04 | 0 | 0.0 | 156 ms | 0 |
| Tue 06 | 0 | 0.0 | 167 ms | 0 |
| Tue 08 | 0 | 0.0 | 731 ms | 0 |
| Tue 10 | 0 | 0.0 | 173 ms | 0 |
| Tue 13 | 0 | 0.0 | 291 ms | 0 |
| Tue 15 | 0 | 0.0 | 748 ms | 0 |
| Tue 17 | 0 | 0.0 | 175 ms | 0 |
| Tue 19 | 0 | 0.0 | 244 ms | 0 |
| Tue 22 | 0 | 0.0 | 82 ms | 0 |
| Wed 00 | 0 | 0.0 | 247 ms | 0 |
| Wed 02 | 0 | 0.0 | 195 ms | 0 |
| Wed 04 | 0 | 0.0 | 276 ms | 0 |
| Wed 07 | 0 | 0.0 | 222 ms | 0 |
| Wed 09 | 0 | 0.0 | 204 ms | 0 |
| Wed 11 | 0 | 0.0 | 199 ms | 0 |
| Wed 13 | 0 | 0.0 | 720 ms | 0 |
| Wed 15 | 0 | 0.0 | 174 ms | 0 |
| Wed 17 | 0 | 0.0 | 61 ms | 0 |
| Wed 20 | 0 | 0.0 | 215 ms | 0 |
| Wed 22 | 0 | 0.0 | 240 ms | 0 |
| Thu 00 | 0 | 0.0 | 180 ms | 0 |
| Thu 02 | 0 | 0.0 | 205 ms | 0 |
| Thu 04 | 0 | 0.0 | 154 ms | 0 |
| Thu 06 | 0 | 0.0 | 199 ms | 0 |
| Thu 08 | 0 | 0.0 | 196 ms | 0 |
| Thu 10 | 0 | 0.0 | 84 ms | 0 |
| Thu 13 | 0 | 0.0 | 274 ms | 0 |
| Thu 15 | 0 | 0.0 | 161 ms | 0 |
| Thu 17 | 0 | 0.0 | 160 ms | 0 |
| Thu 19 | 0 | 0.0 | 375 ms | 0 |
| Thu 21 | 0 | 0.0 | 279 ms | 0 |
| Thu 23 | 0 | 0.0 | 185 ms | 0 |
| Fri 01 | 0 | 0.0 | 160 ms | 0 |
| Fri 03 | 0 | 0.0 | 128 ms | 0 |
| Fri 04 | 0 | 0.0 | 302 ms | 0 |
| Fri 06 | 0 | 0.0 | 49 ms | 0 |
| Fri 08 | 0 | 0.0 | 133 ms | 0 |
| Fri 10 | 0 | 0.0 | 87 ms | 0 |
| Fri 11 | 0 | 0.0 | 266 ms | 0 |
| Fri 13 | 0 | 0.0 | 358 ms | 0 |
| Fri 15 | 0 | 0.0 | 211 ms | 0 |
| Fri 17 | 0 | 0.0 | 164 ms | 0 |
| Fri 19 | 0 | 0.0 | 289 ms | 0 |
| Fri 20 | 0 | 0.0 | 159 ms | 0 |
| Fri 22 | 0 | 0.0 | 205 ms | 0 |
| Sat 00 | 0 | 0.0 | 278 ms | 0 |
| Sat 02 | 0 | 0.0 | 131 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Saddleback Communications 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 Saddleback Communications yet. Outages of 10 minutes or more get their own page here.
Having trouble with Saddleback Communications?
One report per service every 10 minutes from this network. No account.
Follow Saddleback Communications
Get an email when Saddleback Communications goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Saddleback Communications alerts to Slack, Discord or a webhook — free.
About Saddleback Communications
Saddleback Communications is listed in our Social category and checked at saddlebackcomm.com. Saddleback connect businesses and residents in the Salt River Pima-Maricopa Indian Community (SRPMIC) with voice, high speed internet and more.
Saddleback Communications publishes an official status page at status.saddlebackcomm.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with social services: feeds not loading, posts or messages not sending, and login loops.
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: 197 ms average, 49–358 ms range across 14 successful checks.
Questions
Is Saddleback Communications down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Saddleback Communications last down?
We have not recorded a public Saddleback Communications incident since monitoring began 8 days ago.
What is Saddleback Communications's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Saddleback Communications respond?
197 ms on average over the last 24 hours (49–358 ms).
Does Saddleback Communications have an official status page?
Yes, at https://status.saddlebackcomm.com.
Saddleback Communications 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 social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Saddleback Communications here at once, the problem is on Saddleback Communications'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 Saddleback Communications. 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.