bgpreport

Network · data from 2026-11-12

AS8821 WWZ Telekom

Registry name: TELEZUG WWZ Telekom AG, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8821, 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.
2a0d:7a00:4101::/48 No ROA RIR databaseRIPE 634 100% 69
62.171.0.0/17 Valid RIR databaseRIPE 673 100% 66
77.245.176.0/20 Valid RIR databaseRIPE 673 100% 66
82.136.64.0/18 Valid RIR databaseRIPE 673 100% 66
151.248.128.0/17 Valid RIR databaseRIPE 673 100% 66
158.181.96.0/19 Valid RIR databaseRIPE 673 100% 66
185.42.244.0/22 Valid RIR databaseRIPE 673 100% 66
185.244.112.0/22 Valid RIR databaseRIPE 673 100% 66
212.4.64.0/19 Valid RIR databaseRIPE 673 100% 66
217.194.48.0/20 Valid RIR databaseRIPE 673 100% 66
2a01:760::/29 Valid RIR databaseRIPE 635 100% 69
2a01:8b80::/29 Valid RIR databaseRIPE 635 100% 69
2a03:62a0:4101::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS8821: RIPE::AS-TELEZUG. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS8821 isn't in the set, or no route object for AS8821 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS8821 in itNot covered
RIPE::AS-TELEZUG RIPE 9344 Yes 0

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:7a00:4101::/48No ROA covers it. Add a ROA for AS8821, maxLength 48.634 of 636

Route objects not announced

Every route object with origin AS8821 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.