Roxy status

Last 24 hours

1. 06:00 UTC: No data
2. 07:00 UTC: No data
3. 08:00 UTC: No data
4. 09:00 UTC: No data
5. 10:00 UTC: No data
6. 11:00 UTC: No data
7. 12:00 UTC: No data
8. 13:00 UTC: No data
9. 14:00 UTC: No data
10. 15:00 UTC: No data
11. 16:00 UTC: No data
12. 17:00 UTC: No data
13. 18:00 UTC: No data
14. 19:00 UTC: No data
15. 20:00 UTC: No data
16. 21:00 UTC: No data
17. 22:00 UTC: No data
18. 23:00 UTC: No data
19. 00:00 UTC: No data
20. 01:00 UTC: No data
21. 02:00 UTC: No data
22. 03:00 UTC: No data
23. 04:00 UTC: Operational
24. 05:00 UTC: Operational

24 hours agoNow

• Operational
• Degraded
• Paused
• No data

Notes

• Caching: on. Popular answers are reused for about 180 seconds, so data can be a little old.
• Rate limits from Roblox: none active right now.
• Your limit: 10 requests every 50 seconds per IP address. Every request counts toward this limit, cached or not. An answer from Roxy's cache spares Roblox, but it still costs Roxy CPU, memory and bandwidth, and one shared allowance per caller keeps Roxy fair for everyone.

Monitors can poll /health for JSON. The guide explains every status code.