bgpreport

Network · data from 2026-11-12

AS209511 MOSGORTRANS-AS STATE UNITARY ENTERPRISE OF THE CITY OF MOSCOW "MOSGORTRANS"

Registry name: MOSGORTRANS-AS STATE UNITARY ENTERPRISE OF THE CITY OF MOSCOW "MOSGORTRANS", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209511, 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.
213.79.86.0/26 No ROA Nonecovered by 213.79.86.0/24 2 0%low visibility 2
213.79.86.128/26 No ROA Nonecovered by 213.79.86.0/24 2 0%low visibility 2
213.79.91.64/26 No ROA None 2 0%low visibility 2

AS-SET

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

  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none213.79.86.0/26No ROA covers it. Add a ROA for AS209511, maxLength 26.2 of 673
Route object: none213.79.86.0/26No route object for it. A route object for 213.79.86.0/24 with origin AS209511 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209511 in the RIR database for the space.2 of 673
ROA: none213.79.86.128/26No ROA covers it. Add a ROA for AS209511, maxLength 26.2 of 673
Route object: none213.79.86.128/26No route object for it. A route object for 213.79.86.0/24 with origin AS209511 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209511 in the RIR database for the space.2 of 673
ROA: none213.79.91.64/26No ROA covers it. Add a ROA for AS209511, maxLength 26.2 of 673
Route object: none213.79.91.64/26No route object for it. Add a route object with origin AS209511 in the RIR database for the space.2 of 673

Route objects not announced

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

213.79.86.0/24RIPENo 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.