Network · data from 2026-11-12

AS51373 TELKONEKT-AS "TELKONEKT" SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIA

Registry name: TELKONEKT-AS "TELKONEKT" SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIA, PL · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 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

10Route objects not announced registered with origin AS51373, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51373, 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.87.72.0/24	Valid	RIR databaseRIPE	671 100%	68
91.218.156.0/24	Valid	RIR databaseRIPE	671 100%	68
91.218.157.0/24	Valid	RIR databaseRIPE	671 100%	68
91.218.158.0/24	Valid	RIR databaseRIPE	671 100%	68
91.218.159.0/24	Valid	RIR databaseRIPE	671 100%	68
94.24.28.0/24	Valid	RIR databaseRIPE	671 100%	68
178.251.120.0/24	Valid	RIR databaseRIPE	671 100%	68
185.44.216.0/24	Valid	RIR databaseRIPE	671 100%	68
185.44.217.0/24	Valid	RIR databaseRIPE	671 100%	68
185.44.218.0/24	Valid	RIR databaseRIPE	671 100%	68
185.44.219.0/24	Valid	RIR databaseRIPE	671 100%	68
185.80.59.0/24	Valid	RIR databaseRIPE	671 100%	68
193.33.8.0/23	Valid	RIR databaseRIPE	671 100%	68
2001:1a68:14::/48	Valid	RIR databaseRIPE	634 100%	68
2a04:9a40::/29	Valid	RIR databaseRIPE	633 100%	68

AS-SET

AS51373 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 10 are in fix.csv.

Route object: not announced10

Route objects not announced

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


77.87.72.0/22	RIPE	No ROA
77.87.73.0/24	RIPE	Invalid: origin
77.87.74.0/24	RIPE	Invalid: origin
77.87.75.0/24	RIPE	Invalid: origin
91.218.156.0/22	RIPE	Valid
91.224.46.0/23	RIPE	No ROA
185.44.216.0/22	RIPE	Valid
185.80.56.0/24	RIPE	Invalid: origin
193.33.8.0/24	RIPE	Invalid: maxLength
193.33.9.0/24	RIPE	Invalid: maxLength

77.87.72.0/22

RIPE

No ROA

77.87.73.0/24

RIPE

Invalid: origin

77.87.74.0/24

RIPE

Invalid: origin

77.87.75.0/24

RIPE

Invalid: origin

91.218.156.0/22

RIPE

Valid

91.224.46.0/23

RIPE

No ROA

185.44.216.0/22

RIPE

Valid

185.80.56.0/24

RIPE

Invalid: origin

193.33.8.0/24

RIPE

Invalid: maxLength

193.33.9.0/24

RIPE

Invalid: maxLength

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.