bgpreport

Network · data from 2026-11-12

AS51601 Ай-пи-ти-пи

Registry name: IPTP IPTP LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51601, 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.
154.205.0.0/23 Invalid: origin None 2 0%low visibility 2
195.189.120.0/22 Valid RIR databaseRIPE 671 100% 67
2a03:9d40:6000::/36 Valid RIR databaseRIPE 635 100% 67
2a03:9d40:6000::/48 Valid RIR databaseRIPE 635 100% 67
185.65.175.0/24 Valid RIR databaseRADB, RIPE 529 79% 67

AS-SET

AS51601'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 14 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: origin154.205.0.0/23ROAs covering it name AS17561, AS41095, not AS51601. If AS51601 should announce it, add a ROA for AS51601.2 of 673
Route object: none154.205.0.0/23No route object for it. Add a route object with origin AS51601 in the RIR database for the space.2 of 673

Route objects not announced

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

87.239.184.0/22RIPEValid
98.158.110.0/23ARINValid
156.253.184.0/24RADBValid
176.56.170.0/24RIPEValid
176.56.171.0/24RIPEValid
176.56.176.0/22RIPEValid
176.56.190.0/23RIPEValid
185.65.174.0/24RADB, RIPEValid
193.33.70.0/23RIPEValid
2a03:9d40:2100::/40RIPEValid
2a03:9d40:5100::/40RIPEValid
2a03:9d40:ff00::/40RIPEValid

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.