vøiddo · status
everything’s up.
live snapshot of every public surface in the portfolio. probed manually, on the same VPS as the rest of the studio. no fake 99.99% uptime claims — we’ll tell you when something’s broken.
snapshot captured 2026-04-30·method: HTTP HEAD + latency
web surfaces
| host | role | http | latency |
| voiddo.com | apex / portal | 200 | 47 ms |
| scrb.voiddo.com | scrb web app | 200 | 46 ms |
| rankd.voiddo.com | rankd web app | 200 | 44 ms |
| tools.voiddo.com | free tools subportal | 200 | 51 ms |
| extensions.voiddo.com | extensions subportal | 200 | 59 ms |
| games.voiddo.com | games subportal | 200 | 54 ms |
| ai.voiddo.com | ai products subportal | 200 | 51 ms |
api & backend
| host | role | http | latency |
| api.voiddo.com | scrb backend api | 200 | 59 ms |
| play.voiddo.com | void factory mobile api | 200 | 51 ms |
| game.bruh.tools | void factory v1 (telegram) | 200 | 48 ms |
infrastructure
| component | state |
| postgresql 16 | primary db — nominal |
| redis 7 | cache + rate-limit + celery broker — nominal |
| nginx | reverse proxy — all 200 |
| systemd / pm2 | process supervision — all green |
| tls (let’s encrypt) | all certs valid — auto-renewing |
| paddle (billing) | webhook receiver — nominal |
| resend (email) | transactional + lifecycle — nominal |
| gemini api | ai generations — routing law enforced |
recent incidents
| date | service | summary | outcome |
| none in last 14 days | last incident: 2026-04-19, scrb api 502 for 3 minutes during nginx config reload — resolved. |
about this page
this is not a real-time status page. it’s a manual snapshot, refreshed when something on the portfolio ships or breaks. for live external monitoring, we use uptimerobot across every public host (5-minute intervals). errors hit sentry. logs hit structlog.
what we do not have: a paid statuspage.io subscription, automated public uptime feed, sla guarantees, or a real-time dashboard. small studio. trying to be honest about that — running a full status infrastructure for a 6-product portfolio at this stage is overhead, not value.
found something broken? email
support@voiddo.com or check
/security for the responsible-disclosure path. you’ll usually get a reply same-day.