ResearchRouting table, RPKI, IRR & looking glass

AS4883

No registry name is on file for AS4883. It originates 2 prefixes in the global routing table.

2
IPv4 prefixes
0
IPv6 prefixes
2,048
IPv4 addresses
0%
RPKI valid

Who holds AS4883

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

AS number
AS4883
Handle
n/a
Organization
n/a
Country
n/a
ASPA
None published

What AS4883 announces

Prefixes originated by AS4883 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
2
IPv6 prefixes
0
IPv4 addresses
2,048 (8 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
2
ROAs naming AS4883
0
With an IRR route object
2 100%

Announced prefixes

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

IPv4 (2)

RPKI valid   RPKI invalid   no ROA covers it

Who AS4883 buys transit from

Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 1 upstream.

Who buys transit from AS4883

None seen: AS4883 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
RADBAlliantMAINT-AS8001

Route objects with origin AS4883: RADB 8

as-sets that list AS4883 (5)