Operator telemetry · reading paused
NIP (NIBSS Instant Payment)
The operator’s own published status data for NIP (NIBSS Instant Payment). ClearingPost is not reading this source now, so no current operator values are shown. Source: NIBSS Status Page (NIP), published by NIBSS, the system operator, at its status page.
Source · can ClearingPost read it?
Reading pausedClearingPost has paused reading this source until the operator's published data, including how its status labels are defined, has been verified. Nothing is read or shown until then. This says nothing about the service of NIP (NIBSS Instant Payment).
Page generated .
Stored history · ClearingPost's monitor
ClearingPost's monitor is not reading this source and has no stored history of it.
ClearingPost reading · rules, not incidents
Not assessed: there is no current reading to apply ClearingPost's rules to. A missing reading is never read as calm.
Current reading
No current reading.
Nothing is read or shown until ClearingPost is reading this source. Then this page shows, each with the operator's generation time and ClearingPost's read time:
- the operator’s status word for each of the last 60 minutes, and its success rate, response rate and response time;
- operator-reported participant anomalies, as counts only;
- stored history: ClearingPost’s own record of the operator’s minutes over the last 24 hours;
- ClearingPost’s rule readings of that data, which are never incident records.
Stored history · last 24 hours stored by ClearingPost
No stored history yet.
Stored history is ClearingPost’s own dated record of the operator’s per-minute status, success rate and participant-anomaly counts. It is published here after ClearingPost’s monitor has stored readings; nothing is drawn before real readings exist.
What ClearingPost knows about NIP (NIBSS Instant Payment)
Facts
Recorded or published, dated
- Source: NIBSS Status Page (NIP), NIBSS's own status page (monitoring set up 25 September 2026, 10:35 UTC).
Signals
Reports and rule readings, not confirmations
- No current reading, so no rule is evaluated.
Unknowns
What ClearingPost cannot say
- The operator's current telemetry for NIP (NIBSS Instant Payment): reading is paused, so there is no current reading.
- ClearingPost does not measure NIP (NIBSS Instant Payment) itself; these are the operator's own published metrics and status words.
- Which participants are affected: ClearingPost publishes participant anomalies as counts only.
- Whether any operator status reflects an incident: an incident is recorded only after human review, with an authoritative statement.
Evidence
Where it comes from
Evidence timeline
- Monitoring
Monitoring ·
ClearingPost: reading paused, NIBSS Status Page (NIP)
ClearingPost paused reading the operator's page until its published data, including how its status labels are defined, has been verified.
Monitoring ·
ClearingPost: monitoring set up for NIP (NIBSS Instant Payment)
Source: NIBSS Status Page (NIP), the operator's own status page.
ClearingPost records for NIP (NIBSS Instant Payment)
No active operational event is recorded.
Related infrastructure (3)
- NIP (NIBSS Instant Payment) processes payments in NGN (ClearingPost system registry)
- NIP (NIBSS Instant Payment) in jurisdiction Nigeria (ClearingPost system registry)
- NIP (NIBSS Instant Payment) operated by NIBSS (ClearingPost system registry)
How to read this page
- These are the operator's published metrics and status words. ClearingPost does not measure the payment system itself.
- An operator-reported participant anomaly describes that participant's traffic as measured by the operator. ClearingPost shows counts only; a count is not a statement that any participant or the payment system is unavailable.