Skip to main content

AS39208

IPILimited

********************************************************

Registry

Authoritative registration data

AS number
39208
Name
IPILimited
Organisation
********************************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS39208
194.107.248.0/22 IPv4 /22 RPKI not found
195.246.204.0/22 IPv4 /22 not checked
194.107.248.0/24 IPv4 /24 RPKI not found
194.107.249.0/24 IPv4 /24 not checked
194.107.250.0/24 IPv4 /24 RPKI not found
194.107.251.0/24 IPv4 /24 RPKI not found
195.246.205.0/24 IPv4 /24 RPKI not found
195.246.206.0/24 IPv4 /24 RPKI not found
195.246.207.0/24 IPv4 /24 RPKI not found
2a0d:3fc0::/29 IPv6 /29 RPKI not found
2a0d:3fc0::/32 IPv6 /32 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 AS39208
Address families
LINX LON1: Main 1,000 Mbps IPv4 · IPv6
LINX LON2 1,000 Mbps IPv4

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 AS39208 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

36 networks seen before AS39208 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39208 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

16 adjacencies that may be an artefact of collector peering

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.