bgpreport

Network · data from 2026-11-12

AS207693 TELEKABEL-AS Telekabel Ltd.

Registry name: TELEKABEL-AS Telekabel Ltd., HU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207693, 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.
194.156.80.0/23 No ROA Other origin only 668 99% 67
37.9.208.0/21 No ROA RIR databaseRIPE 672 100% 67
37.9.212.0/22 No ROA RIR databaseRIPE 668 99% 67
2a00:5940:8000::/33 No ROA RIR databaseRIPE 635 100% 67
2a00:5940::/32 No ROA RIR databaseRIPE 634 100% 67

AS-SET

AS207693 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 6 are in fix.csv.

  • ROA: none5
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none194.156.80.0/23No ROA covers it. Add a ROA for AS207693, maxLength 23.668 of 673
Route object: none194.156.80.0/23Route objects for it name AS47116. Add a route object with origin AS207693 in the RIR database for the space.668 of 673
ROA: none37.9.208.0/21No ROA covers it. Add a ROA for AS207693, maxLength 21.672 of 673
ROA: none37.9.212.0/22No ROA covers it. Add a ROA for AS207693, maxLength 22.668 of 673
ROA: none2a00:5940:8000::/33No ROA covers it. Add a ROA for AS207693, maxLength 33.635 of 636
ROA: none2a00:5940::/32No ROA covers it. Add a ROA for AS207693, maxLength 32.634 of 636

Route objects not announced

Every route object with origin AS207693 is announced.

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.