Network · data from 2026-11-12

AS201089 Experience Infinity

Registry name: Infinity Experience Infinity technology Internet Service Company Ltd., IQ · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS201089, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201089, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


185.124.148.0/24	Valid	RIR databaseRIPE	671 100%	66
185.124.151.0/24	Valid	RIR databaseRIPE	670 100%	67
193.58.117.0/24	Valid	RIR databaseRIPE	668 99%	65
188.72.40.0/24	Valid	RIR databaseRIPE	667 99%	65

AS-SET

AS201089's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

Route object: not announced4

Route objects not announced

Route objects with origin AS201089 whose prefix no peer sees AS201089 announce. Many are kept on purpose (backup routes, space announced only in some places).


38.127.208.0/24	ARIN	Valid
91.220.41.0/24	RIPE	Valid
185.124.149.0/24	RIPE	Invalid: origin
185.124.150.0/24	RIPE	Valid

38.127.208.0/24

ARIN

Valid

91.220.41.0/24

RIPE

Valid

185.124.149.0/24

RIPE

Invalid: origin

185.124.150.0/24

RIPE

Valid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.