Status
Platform status.
Always transparent.
See the health of every AlleForge service, and stay informed about incidents, maintenance, and platform availability.
Platform status
Everything running smoothly
All Systems Operational
Operational
Healthy
Posted here by our team
Service health
Every service, monitored
Workspace
Core request building and testing environment.
API Testing
Send requests and inspect responses in real time.
Documentation
Guides, references, and quick starts.
Authentication
Login, sessions, and token issuance.
Collaboration
Live cursors, comments, and shared workspaces.
API Reference
Auto-generated, always-synced reference docs.
Mock Server
Simulate API responses before the backend exists.
Monitoring
Uptime and performance tracking for endpoints.
AlleForge Agent
Bridges your browser to localhost and private APIs.
Live infrastructure
Every layer, healthy
A simplified view of the path your requests take through AlleForge.
Browser
OperationalYour request leaves the workspace.
Edge
OperationalRouted through the nearest edge node.
API
OperationalHandled by the AlleForge API layer.
Workspace
OperationalMatched against your saved collection.
Database
OperationalReads and writes committed safely.
Storage
OperationalAttachments and history persisted.
Agent
OperationalBridges requests to localhost and private APIs.
Incident history
Transparent, even when things break
If something breaks, it gets a public entry here — with what happened and how it was fixed.
No incidents reported
Nothing to report yet. When an incident happens, it’ll be logged here — during and after.
What an incident report looks like
Scheduled maintenance
Planned work, communicated early
No maintenance scheduled
There’s nothing planned right now. If that changes, it will show up here well before it happens. Seeing something odd that isn’t reflected here? Let us know.
What a maintenance window looks like
Workspace database upgrade
Expected impact: brief read-only mode for workspace history during the window — testing and requests are unaffected.
Incident lifecycle
How we handle every incident
- 01
Issue Detected
Automated monitoring or a report flags something abnormal.
- 02
Investigation
The on-call team starts digging into logs and metrics.
- 03
Root Cause
The underlying cause is identified and confirmed.
- 04
Fix
A fix is developed, tested, and rolled out.
- 05
Monitoring
The team watches closely to confirm the fix holds under real traffic.
- 06
Resolved
The incident is closed and documented publicly.
Stay informed
Subscribe to status updates
Dedicated notification channels are on the way. Until then, these are the fastest ways to hear from us directly.
RSS Feed
Subscribe with any feed reader.
Webhook
Push incidents into your own systems.
Slack
Get alerts in a dedicated channel.
Discord
Status updates in your server.
Reliability principles
Transparency first.
Monitoring, built to last.
Fast incident response.
Clear communication.
Trust you can verify.
Frequently asked
Questions about our status
This page is updated by our team when something changes — it isn't hooked up to automated monitoring yet, so treat it as what we know, not a live feed.
Notification channels — RSS, webhook, Slack, and Discord — are on the way. For now, Discord and GitHub are the fastest ways to hear from us directly.
Scheduled maintenance is posted here in advance with the affected service, expected duration, and impact — so there are no surprises.
When something breaks, it gets a public entry here with what happened and how it was fixed, posted as soon as our team can write it up.
Webhook notifications are coming soon, so you'll be able to pipe status changes directly into your own alerting systems.
Build with confidence.
A platform you can trust, transparent about status and honest when things break.