bgpreport

Network · data from 2026-11-12

AS205659 CODE200-ISP2 UAB code200

Registry name: CODE200-ISP2 UAB code200, LT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205659, 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.30.24.0/22 No ROA Other IRR onlyRADB 673 100% 67
102.128.167.0/24 No ROA RIR databaseAFRINIC, RADB 673 100% 67
104.233.24.0/23 Valid Other origin only 673 100% 67
104.239.10.0/23 Valid Other origin only 673 100% 67
104.239.76.0/23 Valid Other origin only 673 100% 67
216.173.96.0/22 Valid Other origin only 673 100% 67
216.173.107.0/24 Valid Other origin only 673 100% 67
216.173.110.0/24 Valid Other origin only 673 100% 67
64.190.252.0/22 Valid Other IRR onlyALTDB, BBOI 673 100% 67
216.246.212.0/22 Valid Other IRR onlyALTDB 673 100% 67
31.24.85.0/24 Valid RIR databaseRIPE 673 100% 67
45.14.74.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
109.234.79.0/24 Valid RIR databaseRIPE 673 100% 67
172.98.182.0/24 Valid RIR databaseARIN, RADB 673 100% 67
193.46.221.0/24 Valid RIR databaseRIPE 673 100% 67
5.253.227.0/24 Valid RIR databaseRIPE 672 100% 67
37.16.89.0/24 Valid RIR databaseRIPE 672 100% 67
185.218.232.0/23 Valid RIR databaseRADB, RIPE 668 99% 67
185.218.234.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
185.229.242.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
185.235.12.0/23 Valid RIR databaseRADB, RIPE 668 99% 67
2a13:6cc6::/32 Valid RIR databaseRIPE 634 100% 69
2a13:d3c0::/29 Valid RIR databaseRIPE 631 99% 67

AS-SET

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

  • ROA: none2
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none154.30.24.0/22No ROA covers it. Add a ROA for AS205659, maxLength 22.673 of 673
Route object: RIR154.30.24.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none102.128.167.0/24No ROA covers it. Add a ROA for AS205659, maxLength 24.673 of 673
Route object: none104.233.24.0/23Route objects for it name AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: none104.239.10.0/23Route objects for it name AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: none104.239.76.0/23Route objects for it name AS9009, AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: none216.173.96.0/22Route objects for it name AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: none216.173.107.0/24Route objects for it name AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: none216.173.110.0/24Route objects for it name AS201207. Add a route object with origin AS205659 in the RIR database for the space.673 of 673
Route object: RIR64.190.252.0/22Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
Route object: RIR216.246.212.0/22Route object only in ALTDB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

45.145.214.0/23RADBNo ROA
2a02:e9c6::/32RIPEValid
2a14:c881:8000::/33RIPEValid

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.