Changelog

Monitoring now tells the difference between degraded performance, partial outage, and major outage. Degraded states revert to green once resolved. Outages leave a permanent record for the day. Your status page gives a more accurate picture without false alarms.

When a service degrades or goes down, alerts fire immediately through email and Discord. Each alert includes severity details, affected services, and a direct link to the status page.

Two new sections on foura.ai: a blog for product updates and industry deep-dives, and a docs portal for API reference and integration guides. Both accessible through your FourA account.

Every monitored service now shows 30 days of uptime history. Each day is a color-coded bar: green for operational, yellow for degraded, red for outage. Hover for downtime details. A new Past Incidents section groups resolved incidents by date.

Every FourA service gets health-checked every 10 seconds. The system catches degradation in real time and creates incidents automatically. When a service recovers, the incident closes with a full timestamp for your uptime history.

The status page at updates.foura.ai shows real-time service health and refreshes every 30 seconds. Monitoring creates and resolves incidents automatically. Services are grouped by what matters: Scraping Network, API, Proxy Network, Dashboard, and Auth.

HTTP scraping, browser sessions, and proxy requests each have their own rate limits now. Protects infrastructure during spikes and keeps resource allocation fair across customers. Rate-limited requests show up as a distinct outcome in your dashboard analytics.

Your dashboard now shows per-instance CPU, memory, response times, and active connections in real time. Health badges give instant visibility into service state, and a response time bar shows how you're performing against recommended thresholds.

A new settings interface lets you configure API endpoints with live performance indicators. See active connections, response times, and concurrency limits at a glance. Changes save in batch, so you don't have to update one by one.

All FourA API endpoints and web properties now serve traffic over HTTP/2. Faster page loads, better connection multiplexing, and lower latency for clients making concurrent requests. No changes needed on your end.

You're looking at it. A changelog, status page, roadmap, and issue tracker in one place. Stay informed about what we're building, vote on features, and track incidents in real time.

We killed redundant health checks that were burning resources. The proxy pool is leaner and faster now, with smarter reactivation logic for proxies that go temporarily offline.

See all active sessions, sign out remotely, and manage connected devices from the customer portal. Google-linked accounts get dynamic password fields too.

Every proxy in the network now has a unique compact ID. API responses include which proxy handled the request, so you can debug specific calls or lock a session to a particular exit IP.

Create, rotate, and revoke API keys directly from the dashboard. Each key supports optional IP allowlists and expiry dates for tighter access control.