Skip to main content

AS62296

vitalng

---------------------------------

Registry

Authoritative registration data

AS number
62296
Name
vitalng
Organisation
---------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS62296
185.151.12.0/23 IPv4 /23 not checked
185.151.14.0/24 IPv4 /24 not checked
185.151.15.0/24 IPv4 /24 not checked
2a07:8080::/32 IPv6 /32 RPKI valid
2a07:8084::/32 IPv6 /32 RPKI valid
2a07:8085::/32 IPv6 /32 RPKI valid
2a07:8085:563::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS62296
Address families
Equinix Ashburn 100,000 Mbps IPv4 · IPv6
FCIX 10,000 Mbps IPv4 · IPv6
Frys-IX 100,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS62296 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS62296 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS62296 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 15
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS34927 iFog-GmbH 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6
AS3399 OBE-NET 1 2
v4 v6
AS13786 SEABORN 1 2
v4 v6
AS24961 MYLOC-AS 1 2
v4 v6
AS52320 52320 1 2
v4 v6
AS35280 F5 1 1
v4
AS202365 Chronos 1 1
v4
AS263152 ASN263152 1 1
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.