bgpreport

Network · data from 2026-11-12

AS42611 Zzoomm

Registry name: ZZOOMM Full Fibre Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42611, 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.
149.13.192.0/19 No ROA RIR databaseARIN 672 100% 67
154.28.160.0/20 No ROA RIR databaseARIN 2 0%low visibility 2
154.59.208.0/20 No ROA RIR databaseARIN 2 0%low visibility 2
84.18.224.0/19 Valid RIR databaseRIPE 672 100% 67
85.208.12.0/22 Valid RIR databaseRIPE 672 100% 67
91.193.8.0/22 Valid RIR databaseRIPE 672 100% 67
91.193.8.0/24 Valid RIR databaseRIPE 672 100% 67
2a09:8040::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS42611: RIPE::AS-ZZOOMM. 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 (AS42611 isn't in the set, or no route object for AS42611 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 objectsAS42611 in itNot covered
RIPE::AS-ZZOOMM RIPE 4220 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none149.13.192.0/19No ROA covers it. Add a ROA for AS42611, maxLength 19.672 of 673
ROA: none154.28.160.0/20No ROA covers it. Add a ROA for AS42611, maxLength 20.2 of 673
ROA: none154.59.208.0/20No ROA covers it. Add a ROA for AS42611, maxLength 20.2 of 673

Route objects not announced

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