bgpreport

Network · data from 2026-11-12

AS393417 SDN Communications

Registry name: SDNW-393417 - SDN Communications, US · PeeringDB

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

Announced routes

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

2605:7c80::/32 No ROA Other IRR onlyRADB 634 100% 68
66.115.202.0/24 Valid RIR databaseARIN 673 100% 67
209.151.188.0/22 Valid RIR databaseARIN 672 100% 67
208.53.212.0/24 Valid RIR databaseARIN 80 12% 28
66.231.0.0/24 Valid RIR databaseARIN 36 5%low visibility 22
66.231.7.0/24 Valid RIR databaseARIN 36 5%low visibility 22
66.231.21.0/24 Valid RIR databaseARIN 36 5%low visibility 22
208.53.207.0/24 Valid RIR databaseARIN 36 5%low visibility 22

AS-SET

PeeringDB's irr_as_set for AS393417: AS393417. 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 (AS393417 isn't in the set, or no route object for AS393417 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 objectsAS393417 in itNot covered
AS393417 A single AS number, not a set: AS393417 (this network), 12 route objects.

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2605:7c80::/32No ROA covers it. Add a ROA for AS393417, maxLength 32.634 of 636
Route object: RIR2605:7c80::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

64.33.236.0/24ARINValid
64.33.247.0/24ARINValid
66.115.200.0/24ARINValid
66.128.179.0/24ARINValid

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.