bgpreport

Network · data from 2026-11-12

AS35244 PŸUR - Sued

Registry name: TC-PEPCOM Tele Columbus AG, DE · PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
5Route objects not announced registered with origin AS35244, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35244, 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.
46.128.0.0/16 Valid RIR databaseRIPE 673 100% 66
77.47.0.0/17 Valid RIR databaseRIPE 673 100% 66
83.243.112.0/21 Valid RIR databaseRIPE 673 100% 66
85.233.32.0/19 Valid RIR databaseRIPE 673 100% 66
88.215.64.0/18 Valid RIR databaseRIPE 673 100% 66
95.157.0.0/18 Valid RIR databaseRIPE 673 100% 66
109.125.64.0/18 Valid RIR databaseRIPE 673 100% 66
185.169.204.0/22 Valid RIR databaseRIPE 673 100% 66
193.25.118.0/23 Valid RIR databaseRIPE 673 100% 66
194.105.96.0/21 Valid RIR databaseRIPE 673 100% 66
195.46.44.0/22 Valid RIR databaseRIPE 673 100% 66
195.234.128.0/24 Valid RIR databaseRIPE 672 100% 66
2001:4c50::/32 Valid RIR databaseRIPE 636 100% 67
2a02:2455::/33 Valid RIR databaseRIPE 636 100% 67
2a02:2457:300::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS35244's PeeringDB record names no 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 5 are in fix.csv.

  • Route object: not announced5

Route objects not announced

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

192.88.99.0/24RIPE-NONAUTHNo ROA
194.105.96.0/22RIPEValid
194.105.100.0/23RIPEValid
195.46.46.0/24RIPEValid
2002::/16RIPE-NONAUTHNo 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.