bgpreport

Network · data from 2026-11-12

AS215110 ZeroTunnel

Registry name: ZeroTunnel Jan Hill, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215110, 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.

2a0f:6280:703d::/48 Invalid: origin None 1 0%low visibility 1
2a09:54c3:f8a9::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS215110: AS215110:AS-CUSTOMERS. 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 (AS215110 isn't in the set, or no route object for AS215110 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 objectsAS215110 in itNot covered
AS215110:AS-CUSTOMERS In no IRR database read today.

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

  • ROA: origin1
  • Route object: none1
  • AS-SET: not found1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:6280:703d::/48ROAs covering it name AS218868, AS219207, AS219208, AS219283, not AS215110. If AS215110 should announce it, add a ROA for AS215110.1 of 636
Route object: none2a0f:6280:703d::/48No route object for it. Add a route object with origin AS215110 in the RIR database for the space.1 of 636
AS-SET: not foundAS215110:AS-CUSTOMERSPeeringDB names AS215110:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

2a09:54c3:600e::/48RIPEValid
2a09:54c3:f8a5::/48RIPEValid
2a09:54c3:f8a7::/48RIPEValid
2a0b:4e07:10::/44RIPEValid
2a0b:4e07:2c::/48RIPEValid
2a10:fa82:7000::/36RIPEValid
2a10:fa82:f300::/40RIPEInvalid: origin
2a10:fa82:f302::/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.