bgpreport

Network · data from 2026-11-12

AS48909 CityLine CityLine LLC

Registry name: CityLine CityLine LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48909, 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.
2a07:2280::1/128 No ROA Nonecovered by 2a07:2280::/29 3 0%low visibility 3
95.215.68.0/22 No ROA RIR databaseRIPE 673 100% 66
95.215.68.0/24 No ROA RIR databaseRIPE 673 100% 66
95.215.69.0/24 No ROA RIR databaseRIPE 673 100% 66
95.215.70.0/24 No ROA RIR databaseRIPE 673 100% 66
95.215.71.0/24 No ROA RIR databaseRIPE 673 100% 66
185.141.76.0/22 No ROA RIR databaseRIPE 673 100% 66
185.141.76.0/24 No ROA RIR databaseRIPE 673 100% 66
185.141.77.0/24 No ROA RIR databaseRIPE 673 100% 66
185.141.78.0/24 No ROA RIR databaseRIPE 673 100% 66
185.141.79.0/24 No ROA RIR databaseRIPE 673 100% 66
2a07:2280::/29 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS48909 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 15 are in fix.csv.

  • ROA: none12
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a07:2280::1/128No ROA covers it. Add a ROA for AS48909, maxLength 128.3 of 636
Route object: none2a07:2280::1/128No route object for it. A route object for 2a07:2280::/29 with origin AS48909 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS48909 in the RIR database for the space.3 of 636
ROA: none95.215.68.0/22No ROA covers it. Add a ROA for AS48909, maxLength 22.673 of 673
ROA: none95.215.68.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none95.215.69.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none95.215.70.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none95.215.71.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none185.141.76.0/22No ROA covers it. Add a ROA for AS48909, maxLength 22.673 of 673
ROA: none185.141.76.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none185.141.77.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none185.141.78.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none185.141.79.0/24No ROA covers it. Add a ROA for AS48909, maxLength 24.673 of 673
ROA: none2a07:2280::/29No ROA covers it. Add a ROA for AS48909, maxLength 29.635 of 636

Route objects not announced

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

95.215.68.0/23RIPENo ROA
95.215.70.0/23RIPENo ROA

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.