User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
inthegame.io · Cloud & developer
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 16 min ago. Last stored result reached it in 288 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 342 ms | 0 |
| Tue 01 | 0 | 0.0 | 369 ms | 0 |
| Tue 03 | 0 | 0.0 | 307 ms | 0 |
| Tue 05 | 0 | 0.0 | 281 ms | 0 |
| Tue 07 | 0 | 0.0 | 303 ms | 0 |
| Tue 09 | 0 | 0.0 | 351 ms | 0 |
| Tue 12 | 0 | 0.0 | 241 ms | 0 |
| Tue 14 | 0 | 0.0 | 329 ms | 0 |
| Tue 16 | 0 | 0.0 | 341 ms | 0 |
| Tue 18 | 0 | 0.0 | 309 ms | 0 |
| Tue 21 | 0 | 0.0 | 282 ms | 0 |
| Tue 23 | 0 | 0.0 | 178 ms | 0 |
| Wed 01 | 0 | 0.0 | 248 ms | 0 |
| Wed 03 | 0 | 0.0 | 310 ms | 0 |
| Wed 05 | 0 | 0.0 | 303 ms | 0 |
| Wed 08 | 0 | 0.0 | 217 ms | 0 |
| Wed 10 | 0 | 0.0 | 325 ms | 0 |
| Wed 12 | 0 | 0.0 | 185 ms | 0 |
| Wed 13 | 0 | 0.0 | 216 ms | 0 |
| Wed 15 | 0 | 0.0 | 318 ms | 0 |
| Wed 17 | 0 | 0.0 | 160 ms | 0 |
| Wed 20 | 0 | 0.0 | 206 ms | 0 |
| Wed 22 | 0 | 0.0 | 494 ms | 0 |
| Thu 00 | 0 | 0.0 | 328 ms | 0 |
| Thu 02 | 0 | 0.0 | 373 ms | 0 |
| Thu 04 | 0 | 0.0 | 335 ms | 0 |
| Thu 06 | 0 | 0.0 | 346 ms | 0 |
| Thu 08 | 0 | 0.0 | 340 ms | 0 |
| Thu 10 | 0 | 0.0 | 310 ms | 0 |
| Thu 12 | 0 | 0.0 | 290 ms | 0 |
| Thu 14 | 0 | 0.0 | 362 ms | 0 |
| Thu 16 | 0 | 0.0 | 242 ms | 0 |
| Thu 19 | 0 | 0.0 | 331 ms | 0 |
| Thu 21 | 0 | 0.0 | 302 ms | 0 |
| Thu 23 | 0 | 0.0 | 273 ms | 0 |
| Fri 01 | 0 | 0.0 | 392 ms | 0 |
| Fri 03 | 0 | 0.0 | 178 ms | 0 |
| Fri 05 | 0 | 0.0 | 335 ms | 0 |
| Fri 07 | 0 | 0.0 | 352 ms | 0 |
| Fri 09 | 0 | 0.0 | 275 ms | 0 |
| Fri 11 | 0 | 0.0 | 300 ms | 0 |
| Fri 13 | 0 | 0.0 | 279 ms | 0 |
| Fri 15 | 0 | 0.0 | 229 ms | 0 |
| Fri 17 | 0 | 0.0 | 293 ms | 0 |
| Fri 19 | 0 | 0.0 | 297 ms | 0 |
| Fri 21 | 0 | 0.0 | 268 ms | 0 |
| Fri 23 | 0 | 0.0 | 288 ms | 0 |
| Sat 00 | 0 | 0.0 | 292 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 inthegame 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 inthegame goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send inthegame alerts to Slack, Discord or a webhook — free.
inthegame, at inthegame.io, is one of the Cloud & developer services we monitor. ITG powers in-content CTV advertising: Pause, Double Box, L-Band, Shoppable and Interactive ad units with a rendering SDK, Ad Router, ad server and ITG Demand.
inthegame publishes an official status page at status.inthegame.io; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 287 ms average, 97–433 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public inthegame incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
287 ms on average over the last 24 hours (97–433 ms).
Yes, at https://status.inthegame.io.
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 inthegame here at once, the problem is on inthegame'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 inthegame. 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.