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 46 min ago. Last stored result reached it in 411 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 252 ms | 0 |
| Tue 08 | 0 | 0.0 | 593 ms | 0 |
| Tue 10 | 0 | 0.0 | 666 ms | 0 |
| Tue 13 | 0 | 0.0 | 306 ms | 0 |
| Tue 15 | 0 | 0.0 | 537 ms | 0 |
| Tue 17 | 0 | 0.0 | 337 ms | 0 |
| Tue 19 | 0 | 0.0 | 303 ms | 0 |
| Tue 22 | 0 | 0.0 | 540 ms | 0 |
| Wed 00 | 0 | 0.0 | 256 ms | 0 |
| Wed 02 | 0 | 0.0 | 402 ms | 0 |
| Wed 04 | 0 | 0.0 | 248 ms | 0 |
| Wed 07 | 0 | 0.0 | 422 ms | 0 |
| Wed 09 | 0 | 0.0 | 194 ms | 0 |
| Wed 11 | 0 | 0.0 | 659 ms | 0 |
| Wed 13 | 0 | 0.0 | 514 ms | 0 |
| Wed 15 | 0 | 0.0 | 480 ms | 0 |
| Wed 17 | 0 | 0.0 | 196 ms | 0 |
| Wed 20 | 0 | 0.0 | 212 ms | 0 |
| Wed 22 | 0 | 0.0 | 552 ms | 0 |
| Thu 00 | 0 | 0.0 | 569 ms | 0 |
| Thu 02 | 0 | 0.0 | 179 ms | 0 |
| Thu 04 | 0 | 0.0 | 216 ms | 0 |
| Thu 06 | 0 | 0.0 | 337 ms | 0 |
| Thu 08 | 0 | 0.0 | 335 ms | 0 |
| Thu 10 | 0 | 0.0 | 454 ms | 0 |
| Thu 12 | 0 | 0.0 | 450 ms | 0 |
| Thu 14 | 0 | 0.0 | 446 ms | 0 |
| Thu 17 | 0 | 0.0 | 288 ms | 0 |
| Thu 19 | 0 | 0.0 | 548 ms | 0 |
| Thu 21 | 0 | 0.0 | 463 ms | 0 |
| Thu 23 | 0 | 0.0 | 209 ms | 0 |
| Fri 00 | 0 | 0.0 | 397 ms | 0 |
| Fri 02 | 0 | 0.0 | 520 ms | 0 |
| Fri 04 | 0 | 0.0 | 164 ms | 0 |
| Fri 06 | 0 | 0.0 | 294 ms | 0 |
| Fri 08 | 0 | 0.0 | 136 ms | 0 |
| Fri 10 | 0 | 0.0 | 264 ms | 0 |
| Fri 12 | 0 | 0.0 | 405 ms | 0 |
| Fri 14 | 0 | 0.0 | 249 ms | 0 |
| Fri 16 | 0 | 0.0 | 280 ms | 0 |
| Fri 18 | 0 | 0.0 | 369 ms | 0 |
| Fri 19 | 0 | 0.0 | 248 ms | 0 |
| Fri 20 | 0 | 0.0 | 472 ms | 0 |
| Fri 22 | 0 | 0.0 | 491 ms | 0 |
| Sat 00 | 0 | 0.0 | 399 ms | 0 |
| Sat 02 | 0 | 0.0 | 202 ms | 0 |
| Sat 04 | 0 | 0.0 | 393 ms | 0 |
| Sat 05 | 0 | 0.0 | 411 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 InTouch Receipting 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 InTouch Receipting goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send InTouch Receipting alerts to Slack, Discord or a webhook — free.
InTouch Receipting is listed in our Money category and checked at intouchreceipting.com. InTouch - The Leading K-12 Payments Platform
InTouch Receipting publishes an official status page at status.intouchreceipting.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: 318 ms average, 35–491 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public InTouch Receipting incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
318 ms on average over the last 24 hours (35–491 ms).
Yes, at https://status.intouchreceipting.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 InTouch Receipting here at once, the problem is on InTouch Receipting'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 InTouch Receipting. 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.