Skip to content
Book a Demo
STA.00 / STATUS

Platform status, transparently.

A live look at AfriGRC's platform health, incident history, and scheduled maintenance — built to grow into a fully monitored status portal as our operational program matures.

All Systems Operational

Last Updated: August 5, 2026

Every status, incident, and maintenance entry on this page is illustrative demo data, not a live monitoring feed. This page is built to integrate with real monitoring once that integration is complete.

STA.01 / OPERATIONAL DASHBOARD

The executive summary.

Demo values — a live monitoring integration will populate this dashboard in real time.

9 of 9

Services Operational

Across every platform area.

0

Open Incidents

None currently open.

1

Scheduled Maintenance

Example entry — see below.

5

Regions Covered

Current and planned, across Africa.

Pending Integration

Monitoring Coverage

Built out as our operational program matures.

STA.02 / PLATFORM OVERVIEW

Every product area, at a glance.

  • Platform

    The core AfriGRC web application.

    Operational
  • API

    Programmatic access to the platform for integrations.

    Operational
  • Authentication

    Sign-in, session management, and multi-factor authentication.

    Operational
  • Dashboard

    Executive and operational dashboards across every module.

    Operational
  • Notifications

    In-app and email notifications for platform activity.

    Operational
  • Evidence Storage

    Storage and retrieval of compliance evidence and documents.

    Operational
  • Reporting

    Scheduled and on-demand reports across modules.

    Operational
  • Developer Services

    API documentation, webhooks, and developer tooling.

    Operational
  • Future AI Services

    AI Copilot and other AI-assisted platform functionality.

    Operational
STA.03 / SERVICE HEALTH DASHBOARD

What each status means.

Operational

The service is running normally, with no known issues.

Degraded Performance

The service is available but performing below its normal standard — for example, slower than usual response times.

Partial Outage

Some functionality of the service is unavailable, while the rest continues to operate.

Major Outage

The service is unavailable or unusable for most users.

Maintenance

The service is undergoing planned maintenance that may affect availability.

Unknown

Status has not yet been determined — typically because monitoring for this area is still being configured.

STA.04 / REGIONAL STATUS

Select a region for detail.

West Africa

Includes our Lagos headquarters. Primary region for West African Customers.

STA.05 / COMPONENT STATUS

Infrastructure, browsable by category.

12 results

  • Core Infrastructure

    Authentication

    Operational
  • Core Infrastructure

    API Gateway

    Operational
  • Core Infrastructure

    Background Jobs

    Operational
  • Data

    Database

    Operational
  • Communication

    Notifications

    Operational
  • Communication

    Email Delivery

    Operational
  • Data

    Storage

    Operational
  • Data

    Search

    Operational
  • Data

    Audit Logs

    Operational
  • Core Infrastructure

    Compliance Engine

    Operational
  • AI

    AI Engine (Future)

    Unknown
  • Data

    Document Generation

    Operational
STA.06 / INCIDENT HISTORY

Every incident, filterable.

The two entries below are illustrative examples demonstrating the incident timeline format — neither describes a real historical event.

2 results

Root cause: This is a sample entry demonstrating the incident timeline format — not a real historical event. A real entry would describe the confirmed root cause here.

Postmortem Not Published

Root cause: This is a sample entry demonstrating the incident timeline format — not a real historical event.

Postmortem Not Published

STA.07 / SCHEDULED MAINTENANCE

Select a highlighted date for detail.

The entry below is an illustrative example demonstrating the maintenance card format — not a real scheduled event.

August 2026

SMTWTFS

Example: Database Infrastructure Upgrade

Scheduled

This is a sample entry demonstrating the maintenance card format — not a real scheduled event.

August 17, 2026, 1:00 AM UTC – 3:00 AM UTC

PlatformAPIReporting

Customer impact: Brief read-only mode expected during the maintenance window.

STA.08 / HISTORICAL AVAILABILITY

30 days, 90 days, and 12 months — ready, not yet populated.

No percentage is shown here today, and none will be until a real monitoring integration exists to back it.

Data available after monitoring integration

STA.09 / STATUS SUBSCRIPTIONS

Choose how you want to hear from us.

Available

Email

Get an email when an incident or maintenance event is created, updated, or resolved.

Coming Soon

RSS

A syndicated feed of status updates for any RSS reader.

Coming Soon

Webhook

Push status events directly into your own systems.

Coming Soon

SMS

Text message alerts for major incidents.

Coming Soon

Slack

Post status updates directly into a Slack channel.

Coming Soon

Microsoft Teams

Post status updates directly into a Teams channel.

Subscribe by Email

Get notified when an incident opens, updates, or resolves.

Subscribe by RSS

A feed will be published once real incident and maintenance data exists to syndicate.

Not Yet Published

STA.10 / INCIDENT COMMUNICATION PROCESS

Seven stages, from detection to improvement.

  • 01

    Detection

    An issue is detected — through monitoring once integrated, or reported by a Customer or team member.
  • 02

    Investigation

    The team investigates scope and impact before communicating specifics.
  • 03

    Identification

    Once the affected service and likely cause are confirmed, an incident is opened on this page.
  • 04

    Mitigation

    Steps are taken to reduce customer impact while a full fix is developed.
  • 05

    Resolution

    The issue is fully resolved and services return to normal operation.
  • 06

    Postmortem

    For significant incidents, a postmortem is published explaining root cause and remediation.
  • 07

    Continuous Improvement

    Findings feed back into monitoring, alerting, and operational practices.
STA.11 / OPERATIONAL PRACTICES

How we approach running the platform.

TR.01

Monitoring

Monitoring coverage is being built out as the platform and its infrastructure mature.

TR.02

Observability

Logging and diagnostics designed to make an issue's cause identifiable, not just its symptoms.

TR.03

Security

The same security architecture described in our Trust Centre applies to operational infrastructure.

TR.04

Change Management

Changes to production infrastructure follow a reviewed process before release.

TR.05

Backups

Data is backed up as part of standard operational practice.

TR.06

Disaster Recovery

Recovery planning is part of how we think about infrastructure resilience — not yet a published, tested commitment.

TR.07

Responsible AI Operations

AI-assisted features are operated to the same standard described in our Trust Centre's Responsible AI section.

STA.12 / STATUS FAQ

Frequently Asked Questions.

STA.14 / GET IN TOUCH

Questions about platform reliability?

Reach our support team, explore the security architecture behind the platform, or see it live.

Status — AfriGRC