bgpreport

Network · data from 2026-11-12

AS12688 BAIKALTRANSTELECOM Joint Stock Company TransTeleCom

Registry name: BAIKALTRANSTELECOM Joint Stock Company TransTeleCom, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12688, 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.
5.254.224.0/19 Valid RIR databaseRIPE 672 100% 66
31.47.160.0/19 Valid RIR databaseRIPE 672 100% 66
37.49.160.0/19 Valid RIR databaseRIPE 672 100% 66
141.105.32.0/20 Valid RIR databaseRIPE 672 100% 66
141.105.48.0/21 Valid RIR databaseRIPE 672 100% 66
164.215.80.0/20 Valid RIR databaseRIPE 670 100% 66
185.13.120.0/22 Valid RIR databaseRIPE 670 100% 66

AS-SET

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

  • Route object: not announced12

Route objects not announced

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

5.254.224.0/22RIPEInvalid: maxLength
5.254.228.0/22RIPEInvalid: maxLength
5.254.232.0/21RIPEInvalid: maxLength
5.254.240.0/21RIPEInvalid: maxLength
5.254.248.0/22RIPEInvalid: maxLength
5.254.252.0/22RIPEInvalid: maxLength
31.47.160.0/20RIPEInvalid: maxLength
31.47.176.0/22RIPEInvalid: maxLength
31.47.180.0/23RIPEInvalid: maxLength
141.105.38.0/23RIPEInvalid: maxLength
141.105.40.0/21RIPEInvalid: maxLength
2a01:b580::/32RIPEValid

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.