bgpreport

Network · data from 2026-11-12

AS16202 PŸUR - Mitte

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

17IPv4 routes 100.0% RPKI valid · 100.0% with a route object
15IPv6 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
18Route objects not announced registered with origin AS16202, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16202, 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.
77.64.128.0/17 Valid RIR databaseRIPE 673 100% 66
77.64.128.0/18 Valid RIR databaseRIPE 673 100% 66
77.64.192.0/19 Valid RIR databaseRIPE 673 100% 66
83.221.64.0/19 Valid RIR databaseRIPE 673 100% 66
89.186.128.0/19 Valid RIR databaseRIPE 673 100% 66
92.206.0.0/16 Valid RIR databaseRIPE 673 100% 66
92.206.104.0/22 Valid RIR databaseRIPE 673 100% 66
92.206.108.0/22 Valid RIR databaseRIPE 673 100% 66
92.206.128.0/18 Valid RIR databaseRIPE 673 100% 66
92.206.192.0/18 Valid RIR databaseRIPE 673 100% 66
92.206.204.0/23 Valid RIR databaseRIPE 673 100% 66
92.206.242.0/23 Valid RIR databaseRIPE 673 100% 66
95.168.128.0/19 Valid RIR databaseRIPE 673 100% 66
95.168.128.0/20 Valid RIR databaseRIPE 673 100% 66
95.168.144.0/20 Valid RIR databaseRIPE 673 100% 66
185.44.148.0/22 Valid RIR databaseRIPE 673 100% 66
217.68.160.0/19 Valid RIR databaseRIPE 673 100% 66
2a00:c1a0::/32 Valid RIR databaseRIPE 636 100% 67
2a00:c1a0::/34 Valid RIR databaseRIPE 636 100% 67
2a00:c1a0:4000::/34 Valid RIR databaseRIPE 636 100% 67
2a00:c1a0:8000::/34 Valid RIR databaseRIPE 636 100% 67
2a00:c1a0:c000::/34 Valid RIR databaseRIPE 636 100% 67
2a02:2454:8000::/33 Valid RIR databaseRIPE 636 100% 67
2a02:2454:8000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:9000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:a000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:b000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:c000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:d000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:e000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2454:f000::/36 Valid RIR databaseRIPE 636 100% 67
2a02:2457:100::/40 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS16202'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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

77.64.128.0/19RIPEValid
77.64.160.0/19RIPEValid
77.64.192.0/18RIPEValid
77.64.224.0/19RIPEValid
83.221.64.0/20RIPEValid
83.221.68.0/23RIPEValid
83.221.70.0/23RIPEValid
83.221.80.0/20RIPEValid
83.221.88.0/22RIPEValid
89.186.128.0/20RIPEValid
89.186.144.0/20RIPEValid
92.206.0.0/17RIPEValid
92.206.0.0/18RIPEValid
92.206.64.0/18RIPEValid
92.206.68.0/23RIPEValid
92.206.84.0/23RIPEValid
92.206.244.0/22RIPEValid
185.44.150.0/23RIPEValid

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.