Skip to main content

AS62416

PTServidor

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

Registry

Authoritative registration data

AS number
62416
Name
PTServidor
Organisation
--------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS62416
185.222.8.0/22 IPv4 /22 not checked
185.32.188.0/22 IPv4 /22 not checked
2a00:c560::/29 IPv6 /29 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 AS62416
Address families
DE-CIX Lisbon: DE-CIX Lisbon Peering LAN 10,000 Mbps IPv4 · IPv6
Equinix Lisbon: Equinix IX - LS Metro 10,000 Mbps IPv4 · IPv6
GigaPIX - LAN 1: LAN1 10,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 AS62416 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS62416 in AS paths

Observed upstreams
Families
AS6424 247 682
v4 v6
AS6939 HURRICANE 199 307
v4 v6
AS5533 52 121
v4 v6
AS25091 IP-Max 4 23
v4 v6
AS35280 F5 4 8
v4 v6
AS37468 ORG-AC4-AFRINIC 3 6
v4
AS22356 2 4
v4
AS60171 2 4
v4 v6
AS37282 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS62416 in AS paths

Observed downstreams
Families
AS199993 45 95
v4 v6
AS197000 6 18
v4 v6
AS25152 K-ROOT-SERVER 3 10
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 17
v4 v6
AS37680 3 5
v4
AS61573 2 5
v4 v6

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.