bgpreport

Network · data from 2026-11-12

AS137502 NOMINET-AS-AP - NOMINET UK

Registry name: NOMINET-AS-AP - NOMINET UK, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137502, 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.
2401:fd80:1ff::/48 Valid RIR databaseAPNIC, RADB 635 100% 67
213.248.255.0/24 Valid RIR databaseRADB, RIPE 462 69% 67
43.230.49.0/24 Valid RIR databaseAPNIC, RADB 83 12% 21
43.230.50.0/24 Valid RIR databaseAPNIC, RADB 83 12% 21
43.230.51.0/24 Valid RIR databaseAPNIC, RADB 83 12% 21
213.248.221.0/24 Valid RIR databaseRADB, RIPE 83 12% 21
213.248.222.0/24 Valid RIR databaseRADB, RIPE 83 12% 21
43.230.48.0/24 Valid RIR databaseAPNIC, RADB 82 12% 21
213.248.220.0/24 Valid RIR databaseRADB, RIPE 82 12% 21
213.248.223.0/24 Valid RIR databaseRADB, RIPE 82 12% 21
213.248.216.0/24 Valid RIR databaseRADB, RIPE 67 10%low visibility 33
213.248.217.0/24 Valid RIR databaseRADB, RIPE 67 10%low visibility 33
213.248.254.0/24 Valid RIR databaseRADB, RIPE 67 10%low visibility 34
213.248.218.0/24 Valid RIR databaseRADB, RIPE 66 10%low visibility 33
103.49.80.0/24 Valid RIR databaseAPNIC, RADB 65 10%low visibility 33
103.49.81.0/24 Valid RIR databaseAPNIC, RADB 65 10%low visibility 33
103.49.82.0/24 Valid RIR databaseAPNIC, RADB 65 10%low visibility 33
103.49.83.0/24 Valid RIR databaseAPNIC, RADB 65 10%low visibility 33
213.248.219.0/24 Valid RIR databaseRADB, RIPE 65 10%low visibility 32
2a01:618:404::/48 Valid RIR databaseRADB, RIPE 59 9%low visibility 16
2a01:618:405::/48 Valid RIR databaseRADB, RIPE 59 9%low visibility 16
2a01:618:406::/48 Valid RIR databaseRADB, RIPE 59 9%low visibility 16
2a01:618:407::/48 Valid RIR databaseRADB, RIPE 59 9%low visibility 16
2401:fd80:404::/48 Valid RIR databaseAPNIC, RADB 57 9%low visibility 15
2401:fd80:405::/48 Valid RIR databaseAPNIC, RADB 57 9%low visibility 15
2401:fd80:406::/48 Valid RIR databaseAPNIC, RADB 57 9%low visibility 15
2401:fd80:407::/48 Valid RIR databaseAPNIC, RADB 57 9%low visibility 15
2401:fd80:400::/48 Valid RIR databaseAPNIC, RADB 29 5%low visibility 25
2401:fd80:401::/48 Valid RIR databaseAPNIC, RADB 29 5%low visibility 25
2401:fd80:403::/48 Valid RIR databaseAPNIC, RADB 29 5%low visibility 25
2a01:618:400::/48 Valid RIR databaseRADB, RIPE 29 5%low visibility 24
2a01:618:401::/48 Valid RIR databaseRADB, RIPE 29 5%low visibility 24
2a01:618:403::/48 Valid RIR databaseRADB, RIPE 28 4%low visibility 23

AS-SET

AS137502 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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

43.230.48.0/22RADBNo ROA
51.149.0.0/23RADBNo ROA
103.49.80.0/22RADBNo ROA
213.248.216.0/21RADBNo ROA
213.248.224.0/24RADB, RIPEValid
213.248.225.0/24RADB, RIPEValid
213.248.226.0/24RADB, RIPEValid
213.248.227.0/24RADB, RIPEValid
213.248.254.0/23RADBNo ROA
2401:fd80::/32RADBNo ROA
2401:fd80:402::/48APNIC, RADBValid
2a01:618:200::/48RADB, RIPEValid
2a01:618:201::/48RADB, RIPEValid
2a01:618:202::/48RADB, RIPEValid
2a01:618:203::/48RADB, RIPEValid
2a01:618:402::/48RADB, RIPEValid

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.