2a01:9700:5cc0::/44

Currently announced by AS8376 Jordan, in the routed prefix 2a01:9700:5c00::/40.

Current ASN: AS8376; Jordan
Routed prefix: 2a01:9700:5c00::/40; Most specific route covering this prefix
ASNs over time: 1; 4 announcement records
RIR allocation: RIPENCC; Jordan · 2a01:9700::/29

Routing data · Oct 23, 2026, 14:23 UTC

ASN historyEvery routed prefix covering 2a01:9700:5cc0::/44

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
2a01:9700:5cc0::/44	AS8376	Jordan	Jordan	Before monitoring	2026-10-22 00:20	Stopped
2a01:9700:5c00::/40	AS8376	Jordan	Jordan	Before monitoring	2026-10-23 14:23	Announcing
2a01:9700::/32	AS8376	Jordan	Jordan	Before monitoring	2026-10-23 14:23	Announcing
2a01:9700::/29	AS8376	Jordan	Jordan	Before monitoring	2026-10-23 14:23	Announcing

No more specific routes inside this prefix.

The routes covering this address have had no origin changes since ASNBase started monitoring.

From the RIRs’ delegated statistics files. Shows where the addresses are registered, not where they are used.

Every 2 hours ASNBase takes the bgp.tools global routing table (prefix → origin ASN) and compares it with the previous one. The detected time is the time of that comparison; the actual change can be up to about 2 hours earlier.
Only routes seen by more than 100 bgp.tools peers are listed as changes; routes with less visibility are only kept in the history.
A new announcement counts only if it is still in the next routing table, and a withdrawal only if the prefix is missing from two tables in a row, so short flaps are ignored.
ASNBase has been monitoring since 2026-10-19. “Before monitoring” under “First seen” means the route was already announced when monitoring started; the earlier date is unknown.
Prefixes first seen during the first day of monitoring do not count as new announcements: most of them were simply missing from the table at the moment monitoring started.
Countries and regions follow the ASN’s registration, not the actual location of the IP addresses.