ResearchRouting table, RPKI, IRR & looking glass

AS393417 SDN Communications

AS393417 (SDNW-393417) is registered to SDN Communications in US. It originates 4 prefixes in the global routing table.

3
IPv4 prefixes
1
IPv6 prefixes
1,536
IPv4 addresses
75%
RPKI valid

Who holds AS393417

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS393417
Handle
SDNW-393417
Organization
SDN Communications
Country
US
ASPA
3 providers

What AS393417 announces

Prefixes originated by AS393417 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
3
IPv6 prefixes
1
IPv4 addresses
1,536 (6 /24s)
RPKI valid
3 75%
RPKI invalid
0
RPKI not found
1
ROAs naming AS393417
7
With an IRR route object
4 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (3)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS393417 is reached through

The AS just before AS393417 in the paths our looking glass collectors hold, for 4 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Provider authorization

AS393417 publishes an ASPA naming these providers. 1 AS name it as a provider in theirs. Check a path.

The 1 ASes that name AS393417 as a provider

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RADBSDNWMAINT-AS13576

Route objects with origin AS393417: ARIN 7 · RADB 1

as-sets that list AS393417 (5)