Skip to main content

AS43384

ONAT-AS

=============== IPv4 Routing policy =============

Registry

Authoritative registration data

AS number
43384
Name
ONAT-AS
Organisation
=============== IPv4 Routing 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 AS43384
193.105.164.0/24 IPv4 /24 not checked
193.186.15.0/24 IPv4 /24 not checked
2001:67c:1324::/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 AS43384
Address families
DTEL-IX: PUBLIC 2,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 AS43384 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS43384 in AS paths

Observed upstreams
Families
AS206621 ITKarkas-AS 576 765
v4
AS6939 HURRICANE 121 157
v6
AS42905 LIMANET 4 4
v4
AS29632 NASSIST-AS 3 3
v6
AS8772 NLineLLC 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS43384 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v6
AS48919 UA-CITY-AS 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.