bgpreport

Network · data from 2026-11-12

AS209759 ASMT6 Moy Telecom LLC

Registry name: ASMT6 Moy Telecom LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209759, 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.
78.153.159.0/24 Invalid: maxLength Nonecovered by 78.153.156.0/22 110 16% 46
78.153.135.0/24 No ROA RIR databaseRIPE 673 100% 66
213.181.24.0/22 Valid Nonecovered by 213.181.24.0/21 673 100% 66
213.181.28.0/22 Valid Nonecovered by 213.181.24.0/21 673 100% 66
78.40.220.0/23 Valid RIR databaseRIPE 673 100% 66
78.153.146.0/24 Valid RIR databaseRIPE 673 100% 66
78.153.156.0/22 Valid RIR databaseRIPE 673 100% 66
83.217.204.0/22 Valid RIR databaseRIPE 673 100% 66
178.218.156.0/22 Valid RIR databaseRIPE 673 100% 66
185.246.32.0/22 Valid RIR databaseRIPE 673 100% 66
213.181.20.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: maxLength1
  • ROA: none1
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength78.153.159.0/24ROA 78.153.156.0/22 AS209759 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 78.153.159.0/24.110 of 673
Route object: none78.153.159.0/24No route object for it. A route object for 78.153.156.0/22 with origin AS209759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209759 in the RIR database for the space.110 of 673
ROA: none78.153.135.0/24No ROA covers it. Add a ROA for AS209759, maxLength 24.673 of 673
Route object: none213.181.24.0/22No route object for it. A route object for 213.181.24.0/21 with origin AS209759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209759 in the RIR database for the space.673 of 673
Route object: none213.181.28.0/22No route object for it. A route object for 213.181.24.0/21 with origin AS209759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209759 in the RIR database for the space.673 of 673

Route objects not announced

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

213.181.24.0/21RIPENo 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.