Skip to main content

AS8330

LONAP

LONAP Network AS8330 Policy

Registry

Authoritative registration data

AS number
8330
Name
LONAP
Organisation
LONAP Network AS8330 Policy
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 AS8330
5.57.88.0/21 IPv4 /21 not checked
193.203.5.0/24 IPv4 /24 not checked
2a00:eb20::/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 AS8330
Address families
LONAP: LON0 50,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 AS8330 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS8330 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 215 747
v4 v6
AS44684 MYTHIC 27 72
v4 v6
AS3170 VELOXSERV 19 55
v4 v6
AS5413 Wavenet-AS5413 7 15
v4 v6
AS3213 BOGONS-ASN 2 5
v4 v6
AS39351 ESAB-AS 1 3
v4 v6
AS6204 ZET-NET 1 2
v4
AS39326 HSO-GROUP 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS8330 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 15
v4 v6
AS24482 SGGS-AS-AP 1 12
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS48185 team_blue 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS50300 CUSTDC 1 1
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.