154.94.238.0/24

Currently announced jointly by AS137899 I LAYER LIMITED, AS401701 cognetcloud INC, in the routed prefix 154.94.238.0/24.

Routing data · Nov 1, 2026, 16:26 UTC

ASN historyEvery routed prefix covering 154.94.238.0/24

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
154.94.238.0/24	AS137899	I LAYER LIMITED	Hong Kong SAR China	2026-11-01 10:25	2026-11-01 16:26	Announcing
154.94.238.0/24	AS401701	cognetcloud INC	United States	Before monitoring	2026-11-01 16:26	Announcing
154.94.238.0/23	AS137899	I LAYER LIMITED	Hong Kong SAR China	2026-11-01 10:25	2026-11-01 16:26	Announcing
154.94.238.0/23	AS401701	cognetcloud INC	United States	Before monitoring	2026-11-01 16:26	Announcing
154.94.236.0/22	AS401696	cognetcloud INC	United States	Before monitoring	2026-11-01 16:26	Announcing
154.94.236.0/22	AS401701	cognetcloud INC	United States	Before monitoring	2026-11-01 16:26	Announcing
154.92.0.0/14	AS35916	MultaCOM	United States	Before monitoring	2026-11-01 16:26	Announcing

No more specific routes inside this prefix.

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-11-01 10:25	154.94.238.0/24	Origin added	AS137899	I LAYER LIMITED	AS401701	Hong Kong SAR China
2026-11-01 10:25	154.94.238.0/23	Origin added	AS137899	I LAYER LIMITED	AS401701	Hong Kong SAR China

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.