bgpreport

Network · data from 2026-11-12

AS36318 Zachary Seguin

Registry name: ZSNET - Zachary Seguin, Sole Proprietorship, CA · PeeringDB

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

Announced routes

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

44.27.40.0/24 No ROA None 672 100% 67
44.31.4.0/24 No ROA Other IRR onlyRADB 670 100% 67
44.31.214.0/23 No ROA Other IRR onlyRADB 670 100% 67
23.160.88.0/24 Valid RIR databaseARIN 670 100% 67
104.192.72.0/24 Valid RIR databaseARIN 670 100% 67
2602:815:9000::/44 Valid RIR databaseARIN, RADB 635 100% 69
2602:fed2:7085::/48 Valid RIR databaseARIN 635 100% 69
2602:fed2:718f::/48 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS36318: AS36318:AS-ALL. 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 (AS36318 isn't in the set, or no route object for AS36318 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 objectsAS36318 in itNot covered
AS36318:AS-ALL ALTDB 119 Yes 1
ARIN (also) 119 Yes 1

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none44.27.40.0/24No ROA covers it. Add a ROA for AS36318, maxLength 24.672 of 673
Route object: none44.27.40.0/24No route object for it. Add a route object with origin AS36318 in the RIR database for the space.672 of 673
ROA: none44.31.4.0/24No ROA covers it. Add a ROA for AS36318, maxLength 24.670 of 673
Route object: RIR44.31.4.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.31.214.0/23No ROA covers it. Add a ROA for AS36318, maxLength 23.670 of 673
Route object: RIR44.31.214.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

44.32.248.0/23RADBNo ROA
44.33.0.0/20RADBNo ROA

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.