Network · data from 2026-11-12

AS50436 PŸUR - CIN

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

49IPv4 routes 100.0% RPKI valid · 98.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 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

16Route objects not announced registered with origin AS50436, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50436, 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.


94.139.28.0/23	Valid	Nonecovered by 94.139.16.0/20	673 100%	66
5.28.64.0/18	Valid	RIR databaseRIPE	673 100%	66
5.28.64.0/19	Valid	RIR databaseRIPE	673 100%	66
5.28.96.0/19	Valid	RIR databaseRIPE	673 100%	66
37.120.0.0/17	Valid	RIR databaseRIPE	673 100%	66
82.119.0.0/20	Valid	RIR databaseRIPE	673 100%	66
82.119.16.0/20	Valid	RIR databaseRIPE	673 100%	66
92.206.208.0/24	Valid	RIR databaseRIPE	673 100%	66
92.206.209.0/24	Valid	RIR databaseRIPE	673 100%	66
92.206.214.0/24	Valid	RIR databaseRIPE	673 100%	66
92.206.215.0/24	Valid	RIR databaseRIPE	673 100%	66
92.206.250.0/23	Valid	RIR databaseRIPE	673 100%	66
92.206.254.0/23	Valid	RIR databaseRIPE	673 100%	66
94.139.0.0/19	Valid	RIR databaseRIPE	673 100%	66
94.139.0.0/20	Valid	RIR databaseRIPE	673 100%	66
94.139.16.0/20	Valid	RIR databaseRIPE	673 100%	66
77.64.176.0/23	Valid	RIR databaseRIPE	672 100%	66
77.64.200.0/23	Valid	RIR databaseRIPE	672 100%	66
77.64.202.0/23	Valid	RIR databaseRIPE	672 100%	66
77.64.206.0/23	Valid	RIR databaseRIPE	672 100%	66
77.64.220.0/23	Valid	RIR databaseRIPE	672 100%	66
77.64.238.0/23	Valid	RIR databaseRIPE	672 100%	66
83.221.88.0/22	Valid	RIR databaseRIPE	672 100%	66
89.186.143.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.8.0/21	Valid	RIR databaseRIPE	672 100%	66
92.206.22.0/23	Valid	RIR databaseRIPE	672 100%	66
92.206.32.0/20	Valid	RIR databaseRIPE	672 100%	66
92.206.48.0/20	Valid	RIR databaseRIPE	672 100%	66
92.206.68.0/23	Valid	RIR databaseRIPE	672 100%	66
92.206.76.0/22	Valid	RIR databaseRIPE	672 100%	66
92.206.80.0/22	Valid	RIR databaseRIPE	672 100%	66
92.206.132.0/22	Valid	RIR databaseRIPE	672 100%	66
92.206.139.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.155.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.158.0/23	Valid	RIR databaseRIPE	672 100%	66
92.206.176.0/23	Valid	RIR databaseRIPE	672 100%	66
92.206.178.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.189.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.218.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.235.0/24	Valid	RIR databaseRIPE	672 100%	66
92.206.244.0/22	Valid	RIR databaseRIPE	672 100%	66
95.168.142.0/24	Valid	RIR databaseRIPE	672 100%	66
217.68.167.0/24	Valid	RIR databaseRIPE	672 100%	66
77.64.168.0/24	Valid	RIR databaseRIPE	671 100%	66
77.64.172.0/24	Valid	RIR databaseRIPE	671 100%	66
77.64.183.0/24	Valid	RIR databaseRIPE	671 100%	66
77.64.198.0/24	Valid	RIR databaseRIPE	671 100%	66
77.64.199.0/24	Valid	RIR databaseRIPE	671 100%	66
77.64.249.0/24	Valid	RIR databaseRIPE	671 100%	66
2a02:2455:8000::/36	Valid	RIR databaseRIPE	636 100%	67
2a02:2455:9000::/36	Valid	RIR databaseRIPE	636 100%	67
2a02:2455:a000::/36	Valid	RIR databaseRIPE	636 100%	67

AS-SET

AS50436'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 17 are in fix.csv.

Route object: none1
Route object: not announced16

Change	Prefix or set	Detail	Full-table peers
Route object: none	94.139.28.0/23	No route object for it. A route object for 94.139.16.0/20 with origin AS50436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50436 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

94.139.28.0/23

No route object for it. A route object for 94.139.16.0/20 with origin AS50436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50436 in the RIR database for the space.

673 of 673

Route objects not announced

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


37.120.0.0/18	RIPE	Valid
37.120.64.0/18	RIPE	Valid
77.64.162.0/23	RIPE	Valid
82.119.0.0/19	RIPE	Valid
82.119.0.0/21	RIPE	Valid
82.119.0.0/22	RIPE	Valid
82.119.4.0/22	RIPE	Valid
82.119.8.0/21	RIPE	Valid
82.119.8.0/22	RIPE	Valid
82.119.12.0/22	RIPE	Valid
82.119.16.0/22	RIPE	Valid
82.119.20.0/22	RIPE	Valid
82.119.24.0/22	RIPE	Valid
82.119.28.0/22	RIPE	Valid
92.206.254.0/24	RIPE	Valid
92.206.255.0/24	RIPE	Valid

37.120.0.0/18

RIPE

Valid

37.120.64.0/18

RIPE

Valid

77.64.162.0/23

RIPE

Valid

82.119.0.0/19

RIPE

Valid

82.119.0.0/21

RIPE

Valid

82.119.0.0/22

RIPE

Valid

82.119.4.0/22

RIPE

Valid

82.119.8.0/21

RIPE

Valid

82.119.8.0/22

RIPE

Valid

82.119.12.0/22

RIPE

Valid

82.119.16.0/22

RIPE

Valid

82.119.20.0/22

RIPE

Valid

82.119.24.0/22

RIPE

Valid

82.119.28.0/22

RIPE

Valid

92.206.254.0/24

RIPE

Valid

92.206.255.0/24

RIPE

Valid

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.