bgpreport

Network · data from 2026-11-12

AS59678 SYSTEM36

Registry name: SYSTEM36 SYSTEM36 LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59678, 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.
23.148.232.0/24 Valid RIR databaseARIN 671 100% 67
2602:fa9b::/32 Valid RIR databaseARIN 635 100% 67
2602:fa9b::/37 Valid RIR databaseARIN 635 100% 67
2602:fa9b::/48 Valid RIR databaseARIN 635 100% 67
2a07:54c0:ffee::/48 Valid RIR databaseRIPE 635 100% 67
2602:fa9b:c0::/48 Valid RIR databaseARIN 3 0%low visibility 3
2a07:54c2:b00b::/48 Valid RIR databaseRIPE 3 0%low visibility 3
2a06:a005:2c60::/44 Valid RIR databaseRIPE 1 0%low visibility 1
2a0a:6040:4b00::/40 Valid RIR databaseRIPE 1 0%low visibility 1
2a0f:b241:15::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS59678: AS59678:AS-SYS36. 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 (AS59678 isn't in the set, or no route object for AS59678 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 objectsAS59678 in itNot covered
AS59678:AS-SYS36 RIPE9 member sets in no database: AS-ANODYNE, AS-DFL, AS-ZH-NET, AS203867:AS-CUSTOMERS, AS47272:AS-HYEHOST-CA … 1,80917226,466 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 12 are in fix.csv.

  • AS-SET: missing member9
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS-ANODYNE; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS-DFL; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS-ZH-NET; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS203867:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS47272:AS-HYEHOST-CA; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS47272:AS-HYEHOST-EU; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS47272:AS-HYEHOST-US; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS60223:AS-NETIFACE; no IRR database read has it.
AS-SET: missing memberAS59678:AS-SYS36AS59678:AS-SYS36 (RIPE) lists AS9423:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

140.235.128.0/22ARINValid
140.235.128.0/24ARINValid
2a0f:b241:123::/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.