Skip to content
◆ClearingPost

Operations

Operational intelligence

What ClearingPost can evidence about payment-system operations: confirmed events, the systems it monitors, the state of its sources, and what remains unknown.

Assessment built from ClearingPost’s stored records (the page build time, not a read of any operator’s service).

Systems monitored
1 of 149Operator telemetry: NIP (NIBSS Instant Payment)The other 148 are not monitored; their service condition is not assessed
Operator sources enabled for reading
0 of 1NIBSS Status Page (NIP): reading pausedWhether ClearingPost can read a source, not system health
Latest stored operator reading
None yetStored once reading is enabled
Confirmed operational events
0None active, confirmed by an authoritative sourceNo unconfirmed report recorded

What ClearingPost knows

Facts

Recorded or published, dated

  • No active operational event confirmed by an authoritative source is recorded.
  • 4 maintenance windows are scheduled in the next 30 days (next: FedACH / Nacha, 12 October 2026, 00:00–21:30 UTC).

Signals

Reports and rule readings, not confirmations

  • No unconfirmed report is recorded.
  • Operator telemetry signals appear only on the telemetry page, dated; they are never counted as events.

Unknowns

What ClearingPost cannot say

  • 148 of the 149 registry systems are not monitored: ClearingPost does not assess their current service condition.
  • An empty list is not evidence that nothing is happening; it means ClearingPost holds no such record.
  • NIP (NIBSS Instant Payment): reading is paused, so there is no current operator reading.

Evidence

Where it comes from

Monitored systems

NIP (NIBSS Instant Payment)

Nigeria · Operator telemetry · NIBSS

Reading paused
Source
NIBSS Status Page (NIP) · published by NIBSS, the system operator (authoritative for NIP (NIBSS Instant Payment))
Reading
ClearingPost 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).
Stored history
None stored yet.
Operational events
No active operational event recorded for this system.
Telemetry signals
Automatic telemetry signals are shown on the telemetry page only and are never counted as events.

Operator status, last 24 hours stored

No stored readings yet. Once ClearingPost’s monitor is reading this source, the operator’s per-minute status appears here as stored history.

Operator telemetry for NIP (NIBSS Instant Payment) →System pageNigeria operations

Source health — ClearingPost’s ability to read sources

Whether ClearingPost can read an operator’s published data. This is never a statement about the payment system’s service.

Evidence timeline

  • Monitoring
  • Earlier record

  1. 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.

  2. Monitoring ·

    ClearingPost: monitoring set up for NIP (NIBSS Instant Payment)

    Source: NIBSS Status Page (NIP), the operator's own status page.

  3. Earlier record ·

    T2 non-optional maintenance suspending euro and Danish krone settlement

    Incident, T2 / TARGET.

    Source: pymnts.com

  4. Earlier record ·

    T2 processing disruption

    Incident, T2 / TARGET.

    Source: pymnts.com

Event register

ClearingPost monitors 1 of 149 registry systems (operator telemetry: NIP (NIBSS Instant Payment)). Everything else here is recorded events and register data. Each row states its evidence class and links its source.

Filter the register

Upcoming maintenance (next 30 days)

Regulatory and scheme deadlines (next 180 days)

Nothing recorded as of in: active incidents, unconfirmed reports, other active events, migrations and releases.

Recent records

  • IncidentEarlier record, one source per record
    T2 non-optional maintenance suspending euro and Danish krone settlement
    Recorded date: · T2 / TARGET · Earlier incident record · Source: pymnts.com
    Source Established (T2) · Operator acknowledgement not recorded
  • IncidentEarlier record, one source per record
    T2 processing disruption
    Recorded date: · T2 / TARGET · Earlier incident record · Source: pymnts.com
    Source Established (T2) · Operator acknowledgement not recorded
  • IncidentEarlier record, one source per record
    FedACH multi-hour processing delay
    Recorded date: · FedACH / Nacha · Earlier incident record · Source: frbservices.org
    Source tier not recorded · Operator acknowledged