ResearchRouting table, RPKI, IRR & looking glass

AS16699 Hensel Phelps

AS16699 (US-HENSELPHELPS-AS01) is registered to Hensel Phelps in US. It originates 1 prefix in the global routing table.

1
IPv4 prefixes
0
IPv6 prefixes
256
IPv4 addresses
0%
RPKI valid

Who holds AS16699

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

AS number
AS16699
Handle
US-HENSELPHELPS-AS01
Organization
Hensel Phelps
Country
US
ASPA
None published

What AS16699 announces

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

IPv4 prefixes
1
IPv6 prefixes
0
IPv4 addresses
256 (1 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
1
ROAs naming AS16699
0
With an IRR route object
1 100%

Announced prefixes

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

IPv4 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS16699 buys transit from

Inferred from the AS paths in the RouteViews tables, refreshed every 4 hours, most-seen first. 1 upstream.

Who buys transit from AS16699

None seen: AS16699 does not appear to provide transit to anyone.

Routing registry objects

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

Sourceas-nameMaintained by
RADBCharterCommMAINT-CHTR-WD

Route objects with origin AS16699: RADB 1

as-sets that list AS16699 (2)