bgpreport

Network · data from 2026-11-12

AS51837 NETEX-51837-AS iNet Ltd

Registry name: NETEX-51837-AS iNet Ltd, SC · not in PeeringDB

0IPv4 routes
6IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS51837, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51837, 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.
2a0a:f582::/32 No ROA RIR databaseRIPE 635 100% 69
2a0a:f586::/32 No ROA RIR databaseRIPE 635 100% 69
2a0e:eec7::/32 No ROA RIR databaseRIPE 635 100% 69
2a0e:fb46::/32 No ROA RIR databaseRIPE 635 100% 69
2a0f:6fc2::/32 No ROA RIR databaseRIPE 635 100% 69
2a0f:c083::/32 No ROA RIR databaseRIPE 635 100% 69

AS-SET

AS51837 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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:f582::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636
ROA: none2a0a:f586::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636
ROA: none2a0e:eec7::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636
ROA: none2a0e:fb46::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636
ROA: none2a0f:6fc2::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636
ROA: none2a0f:c083::/32No ROA covers it. Add a ROA for AS51837, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS51837 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.