bgpreport

Network · data from 2026-11-12

AS12027 Hytron Network Services (US) LLC - AS12027

Registry name: HYTRON-CA - Hytron Network Services (US) LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12027, 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.
82.41.34.0/24 Valid Nonecovered by 82.41.34.0/23 669 99% 67
82.41.35.0/24 Valid Nonecovered by 82.41.34.0/23 669 99% 67
82.41.34.0/23 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS12027: AS-HYTRON. 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 (AS12027 isn't in the set, or no route object for AS12027 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 objectsAS12027 in itNot covered
AS-HYTRON RADBlists itself further down4 member sets in no database: AS-PUMPCLOUD, AS-REDUCED, AS139855:AS-ALL, AS212233:AS-ECHK 1,308148172,352 Yes 0
ARIN (also)lists itself further down30 member sets in no database: AS-AISANIE-GLOBAL, AS-CHIMON, AS-DUOTU, AS-EOIX, AS-IMCLOUD … 1,02217166,107 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 7 are in fix.csv.

  • Route object: none2
  • AS-SET: missing member4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none82.41.34.0/24No route object for it. A route object for 82.41.34.0/23 with origin AS12027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12027 in the RIR database for the space.669 of 673
Route object: none82.41.35.0/24No route object for it. A route object for 82.41.34.0/23 with origin AS12027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12027 in the RIR database for the space.669 of 673
AS-SET: missing memberAS-HYTRONAS-HYTRON (RADB) lists AS-PUMPCLOUD; no IRR database read has it.
AS-SET: missing memberAS-HYTRONAS-HYTRON (RADB) lists AS-REDUCED; no IRR database read has it.
AS-SET: missing memberAS-HYTRONAS-HYTRON (RADB) lists AS139855:AS-ALL; no IRR database read has it.
AS-SET: missing memberAS-HYTRONAS-HYTRON (RADB) lists AS212233:AS-ECHK; no IRR database read has it.

Route objects not announced

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

204.107.12.0/22RADBNo 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.