ResearchRouting table, RPKI, IRR & looking glass

AS16970 MIDnet

AS16970 (MIDNET) is registered to MIDnet in US. It originates 17 prefixes in the global routing table.

16
IPv4 prefixes
1
IPv6 prefixes
4,096
IPv4 addresses
100%
RPKI valid

Who holds AS16970

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

AS number
AS16970
Handle
MIDNET
Organization
MIDnet
Country
US
ASPA
2 providers

What AS16970 announces

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

IPv4 prefixes
16
IPv6 prefixes
1
IPv4 addresses
4,096 (16 /24s)
RPKI valid
17 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS16970
17
With an IRR route object
17 100%

Announced prefixes

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

Who AS16970 is reached through

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

Provider authorization

AS16970 publishes an ASPA naming these providers. 2 ASes name it as a provider in theirs. Check a path.

The 2 ASes that name AS16970 as a provider

Routing registry objects

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

Sourceas-nameMaintained by
NTTCOMASN-MIDNETMAINT-MIDNET

Route objects with origin AS16970: NTTCOM 17

as-sets that list AS16970 (6)