Network · data from 2026-11-12

AS202264 DMESG-ICT-LTD DMESG ICT Ltd

Registry name: DMESG-ICT-LTD DMESG ICT Ltd, GB · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 40.0% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

0Route objects not announced registered with origin AS202264, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202264, 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.


87.229.97.0/24	Invalid: origin	Other origin only	1 0%low visibility	3
82.38.10.0/24	Valid	Nonecovered by 82.38.10.0/23	672 100%	66
82.38.11.0/24	Valid	Nonecovered by 82.38.10.0/23	672 100%	66
78.105.176.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
82.38.10.0/23	Valid	RIR databaseRADB, RIPE	673 100%	66

87.229.97.0/24

Invalid: origin

Other origin only

1 0%low visibility

82.38.10.0/24

Valid

Nonecovered by 82.38.10.0/23

672 100%

82.38.11.0/24

Valid

Nonecovered by 82.38.10.0/23

672 100%

78.105.176.0/24

Valid

RIR databaseRADB, RIPE

673 100%

82.38.10.0/23

Valid

RIR databaseRADB, RIPE

673 100%

AS-SET

AS202264 isn't in PeeringDB, where networks name their 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.

ROA: origin1
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	87.229.97.0/24	ROAs covering it name AS198377, not AS202264. If AS202264 should announce it, add a ROA for AS202264.	1 of 673
Route object: none	87.229.97.0/24	Route objects for it name AS198377. Add a route object with origin AS202264 in the RIR database for the space.	1 of 673
Route object: none	82.38.10.0/24	No route object for it. A route object for 82.38.10.0/23 with origin AS202264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202264 in the RIR database for the space.	672 of 673
Route object: none	82.38.11.0/24	No route object for it. A route object for 82.38.10.0/23 with origin AS202264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202264 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

87.229.97.0/24

ROAs covering it name AS198377, not AS202264. If AS202264 should announce it, add a ROA for AS202264.

1 of 673

Route object: none

87.229.97.0/24

Route objects for it name AS198377. Add a route object with origin AS202264 in the RIR database for the space.

1 of 673

Route object: none

82.38.10.0/24

No route object for it. A route object for 82.38.10.0/23 with origin AS202264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202264 in the RIR database for the space.

672 of 673

Route object: none

82.38.11.0/24

672 of 673

Route objects not announced

Every route object with origin AS202264 is announced.

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.