bgpreport

Network · data from 2026-11-12

AS218839 ZONEKTELECOM-AS

Registry name: ZONEKTELECOM-AS ZONEK TELECOM LTD, GB · PeeringDB

0IPv4 routes
12IPv6 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
2Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS218839, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS218839, 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.
2a0e:4001:503::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:4001:506::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:4001:507::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:4001:508::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:4001:801::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:4001:509::/48 Valid RIR databaseRIPE 635 100% 69
2a0e:4001:501::/48 Valid RIR databaseRIPE 634 100% 69
2a0e:4001:802::/48 Valid RIR databaseRIPE 633 100% 69
2a0e:4001:505::/48 Valid RIR databaseRIPE 631 99% 67
2a0e:4001:504::/48 Valid RIR databaseRIPE 630 99% 67
2a0e:4001:502::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0e:4001:800::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

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

  • Route object: not announced7

Route objects not announced

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

2a0e:4001:500::/40RIPEValid
2a0e:4001:500::/48RIPEValid
2a0e:4001:510::/48RIPEValid
2a0e:4001:511::/48RIPEValid
2a0e:4001:800::/40RIPEValid
2a0e:4001:803::/48RIPEValid
2a0e:4001:804::/48RIPEValid

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.