Status

Uptime we measure, including the bad minutes.

Every minute RoSignal makes a real request against the same public endpoint your Roblox servers talk to, times it, and stores the result. The numbers below are those checks - nothing is smoothed and nothing is hidden.

MeasuringLoading checks...

Last 24 hours

-

0 checks

Last 7 days

-

Last 30 days

-

Typical response time

-

Median over the last 7 days

Slow response time

-

95th percentile over the last 7 days

Last 90 days

One bar per day. Green is a clean day, dim green means at least one failed check, red means more than 1% of that day's checks failed.

No days recorded yet.

Failed checks

No failed checks in the recorded window.

How to read this

  • Measuring since -. RoSignal is a young product - it isn't going to claim years of history it doesn't have.
  • Checks run once a minute. A blip shorter than that can pass unrecorded, so treat this as a minute-resolution record rather than a perfect one.
  • A short outage costs you no data. The RoSignal module inside your game counts events locally and merges them across servers, retrying the upload until it lands. If the API is briefly unreachable, your counts still arrive - which matters more to your game than the second decimal place above.
  • Your game keeps running regardless. Config values are cached in your servers, so players never see a RoSignal problem - you just can't push a change until it's back.