Where to check Billora's status? The "Service status" page

What is the "Service status" page for?

When Billora feels slow or stops responding, the Service status page tells you within seconds whether the problem comes from the platform (incident, outage, maintenance) or from your side (internet connection, browser). It shows the state of each component, the availability over the last 90 days, ongoing and past incidents and planned maintenance.

Example. Amine can no longer download a PDF. He opens the Service status page: the banner reads "Partially degraded service" and the "Document generation" component is "Degraded", with an "Investigating" incident published twenty minutes ago. He knows the team is already on it and tries again later, without opening a support request.

1. Open the page

1. On the Billora website, open the Resources menu then click Service status (the same link is in the footer): the page opens in a new tab.
2. Or open status.billora.ma directly (the former address billora.ma/status also leads there).

The page exists in French, English and Arabic (right to left). It refreshes automatically: allow one to two minutes at most between a change and its display.

2. Read the global status banner

The large banner at the top summarises the whole service: it is the most serious state among your components.

Banner	What it means
"All systems operational"	All measured components work normally and no incident is ongoing.
"Maintenance in progress"	Maintenance is under way on at least one component (see section 5).
"Partially degraded service"	At least one component is slow or degraded.
"Partial outage in progress"	Part of the service is not responding.
"Major outage in progress"	An essential component is unavailable.
"Service status temporarily unavailable"	No recent measurement is available: the page does not claim everything is fine.
"Measurements starting"	The first automatic checks have not run yet (for example right after monitoring was put into service): the status of each component will appear within the next few minutes. The page does not say everything is fine as long as no measurement exists.

If some measurements are missing, a note says so: "Some measurements are temporarily unavailable: those components are not shown as operational."

3. Understand the state of each component

The "Components" list details seven services. Each has a status badge and an availability bar.

Component	What it covers
Web application	Dashboard and public pages
Database	Business data storage
API & authentication	Login and application endpoints
Document generation	Invoices, quotes, credit notes as PDF
Email sending	Sending documents and reminders
File storage	Logos, receipts, archives
DGI electronic invoicing	Compliance ready — DGI portal open at the reform

State	Meaning
"Operational"	The component works normally.
"Maintenance"	Maintenance is under way on this component.
"Degraded"	The component works but with difficulties (minor-impact incident).
"Partial outage"	The component does not respond correctly (one failed measurement, or a major-impact incident).
"Major outage"	The component is unavailable (three failed measurements in a row, or a critical-impact incident).
"Coming soon"	The component is not open yet. This is the case for DGI electronic invoicing until the platform activates it.
"Not measured"	The last measurement is missing or too old: Billora does not claim the component works.

How is the state measured?

Automatic checks run every 5 minutes on the database, the API and file storage (when enabled). The connection to Billora's email-sending server is checked about every 30 minutes, without sending any message, and document generation about every hour, by rendering a minimal PDF in memory. These checks neither read nor write any customer data. The state shown is the most serious between the latest measurement and the incidents or maintenance published by the team. An outage can take up to about ten minutes to appear (check frequency and page refresh delay).

4. Read the 90-day bar

Under each component, the bar shows the last 90 days: one stroke per day, the most recent at the end ("Today"), the oldest at the start ("90 days ago"). Next to the bar is the average availability: "…% uptime over 90 days", or "…% uptime since …" when the component has been measured for less than 90 days (the percentage then only covers the measured days), or "No measurement yet" if the component has not been measured yet.

Stroke colour	Day concerned
Green	Availability of at least 99% and no incident; or a day without measurement for which no incident was reported (tooltip "no incident reported", day not counted in the percentage).
Yellow	Availability between 95% and 99%, or a minor-impact incident.
Orange	Availability between 80% and 95%, or a major-impact incident.
Red	Availability below 80%, or a critical-impact incident.
Blue	Maintenance that day.
Grey	No data that day.

Hover over a stroke: a tooltip gives the date and the day's availability, for example "17 October 2026: 99.65% uptime", then the title of that day's incidents or maintenance. When several situations add up, the day's colour is the most serious one. Days are counted in UTC. Checks that fail during maintenance do not count in the percentage. On a small screen, the bar only shows the last 30 days; the availability shown always covers the same period as on a large screen.

5. Follow an incident or maintenance

Above the components list, the page shows three blocks, only when they have content: "Ongoing incidents", "Maintenance in progress" and "Scheduled maintenance".

An incident

Each incident is a card with its title, its impact, the affected components and a dated message thread, the most recent on top. The status moves forward like this:

1. "Investigating": the team has noticed the problem and is looking for the cause.
2. "Identified": the cause is known and the fix is under way.
3. "Monitoring": the fix is done and the team checks that everything is stable.
4. "Resolved": the incident is over. It moves to "Past incidents".

The impact is shown by a badge: "Information", "Minor impact", "Major impact" or "Critical impact".

A maintenance

Planned maintenance shows its time window, for example "From 3 Nov, 01:00 to 3 Nov, 02:00 (UTC)", and goes from "Scheduled" to "In progress" then "Completed". The affected components are listed on the card. When the team puts the platform in maintenance, a "Platform maintenance" card appears automatically.

Message language

Messages are shown in the page language when a translation exists. Otherwise the French text is shown, marked "Text in French".

6. Browse the history

The "Past incidents" section ("Last 90 days") groups, day by day, resolved incidents and completed maintenance, with their full thread. If there is nothing: "No incident or maintenance in the last 90 days."

7. Report a problem

1. Check the page first: the incident may already be known.
2. If it is not listed, write to us via the Contact page (link at the bottom of the page), stating the time, the screen concerned and the message shown.

Email subscription to incidents does not exist yet: check the page whenever in doubt.

Frequently asked questions

The page says "All systems operational" but I have a problem. What should I do?

The problem may come from your connection or browser (try a full reload or another browser), or affect your account only. If it persists, contact support with the time and the exact message.

Why is a component "Not measured"?

Its last automatic measurement is missing or too old. Billora prefers to say so rather than show "Operational" without proof. It is not an outage in itself.

Why is DGI electronic invoicing "Coming soon"?

The DGI portal is not yet open for electronic invoicing: until the platform activates it, this component is not measured and is never shown as operational. See also Activate electronic invoicing in Billora.

Does the page replace an availability commitment?

No. It reports the observed state of the service; it is not a contractual service-level commitment.

Next steps

• The first 5 things to do
• Understanding plans and limits