Skip to main content

AS35399

ITIO-AS

Online50 Limited

Registry

Authoritative registration data

AS number
35399
Name
ITIO-AS
Organisation
Online50 Limited
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS35399
87.236.56.0/21 IPv4 /21 not checked
87.236.56.0/22 IPv4 /22 not checked
87.236.60.0/22 IPv4 /22 not checked
87.236.56.0/24 IPv4 /24 not checked
87.236.57.0/24 IPv4 /24 not checked
87.236.58.0/24 IPv4 /24 not checked
87.236.59.0/24 IPv4 /24 not checked
87.236.60.0/24 IPv4 /24 not checked
87.236.61.0/24 IPv4 /24 not checked
87.236.62.0/24 IPv4 /24 not checked
87.236.63.0/24 IPv4 /24 not checked
2a03:b300::/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 AS35399
Address families
LINX LON1: Main 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 AS35399 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

45 networks seen before AS35399 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS35399 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

30 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.