bgpreport

Network · data from 2026-11-12

AS35025 TC-AS AO Teleconnect

Registry name: TC-AS AO Teleconnect, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35025, 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.
91.197.64.113/32 No ROA Nonecovered by 91.197.64.0/22 1 0%low visibility 1
213.5.49.114/32 No ROA Nonecovered by 213.5.49.0/24 1 0%low visibility 1
91.197.64.0/22 No ROA RIR databaseRIPE 673 100% 66
194.126.168.0/22 No ROA RIR databaseRIPE 673 100% 66
213.5.48.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.49.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.50.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.51.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.52.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.53.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.54.0/24 No ROA RIR databaseRIPE 673 100% 66
213.5.55.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none12
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none91.197.64.113/32No ROA covers it. Add a ROA for AS35025, maxLength 32.1 of 673
Route object: none91.197.64.113/32No route object for it. A route object for 91.197.64.0/22 with origin AS35025 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS35025 in the RIR database for the space.1 of 673
ROA: none213.5.49.114/32No ROA covers it. Add a ROA for AS35025, maxLength 32.1 of 673
Route object: none213.5.49.114/32No route object for it. A route object for 213.5.49.0/24 with origin AS35025 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS35025 in the RIR database for the space.1 of 673
ROA: none91.197.64.0/22No ROA covers it. Add a ROA for AS35025, maxLength 22.673 of 673
ROA: none194.126.168.0/22No ROA covers it. Add a ROA for AS35025, maxLength 22.673 of 673
ROA: none213.5.48.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.49.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.50.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.51.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.52.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.53.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.54.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673
ROA: none213.5.55.0/24No ROA covers it. Add a ROA for AS35025, maxLength 24.673 of 673

Route objects not announced

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

194.126.168.0/24RIPENo ROA
194.126.169.0/24RIPENo ROA
194.126.170.0/24RIPENo ROA
194.126.171.0/24RIPENo ROA
213.5.48.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.