Skip to main content

AS6718

NAV

NAV Communications

Registry

Authoritative registration data

AS number
6718
Name
NAV
Organisation
NAV Communications
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

40

IPv6 prefixes

17

Total announced

57

Announced prefixes

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

Prefixes announced by AS6718
193.93.142.0/23 IPv4 /23 not checked
128.0.34.0/24 IPv4 /24 RPKI valid
128.0.36.0/24 IPv4 /24 not checked
185.235.78.0/24 IPv4 /24 RPKI not found
185.36.252.0/24 IPv4 /24 not checked
193.162.136.0/24 IPv4 /24 not checked
195.206.164.0/24 IPv4 /24 not checked
37.156.37.0/24 IPv4 /24 RPKI valid
5.154.224.0/24 IPv4 /24 RPKI valid
80.96.42.0/24 IPv4 /24 RPKI valid
80.97.49.0/24 IPv4 /24 RPKI valid
81.180.207.0/24 IPv4 /24 RPKI valid
85.120.222.0/24 IPv4 /24 RPKI valid
85.120.223.0/24 IPv4 /24 RPKI valid
89.35.4.0/24 IPv4 /24 not checked
89.35.5.0/24 IPv4 /24 RPKI valid
89.37.187.0/24 IPv4 /24 not checked
89.40.133.0/24 IPv4 /24 not checked
89.43.240.0/24 IPv4 /24 RPKI valid
89.43.241.0/24 IPv4 /24 not checked
89.43.242.0/24 IPv4 /24 RPKI valid
89.43.243.0/24 IPv4 /24 RPKI valid
89.43.244.0/24 IPv4 /24 not checked
89.43.245.0/24 IPv4 /24 not checked
89.43.246.0/24 IPv4 /24 not checked
89.43.247.0/24 IPv4 /24 not checked
89.46.24.0/24 IPv4 /24 not checked
89.46.25.0/24 IPv4 /24 RPKI valid
89.46.27.0/24 IPv4 /24 RPKI valid
89.46.28.0/24 IPv4 /24 not checked
89.46.29.0/24 IPv4 /24 RPKI valid
89.46.30.0/24 IPv4 /24 RPKI valid
89.46.31.0/24 IPv4 /24 not checked
91.208.75.0/24 IPv4 /24 RPKI valid
91.239.230.0/24 IPv4 /24 not checked
92.114.88.0/24 IPv4 /24 RPKI valid
92.114.89.0/24 IPv4 /24 not checked
92.114.90.0/24 IPv4 /24 not checked
92.114.91.0/24 IPv4 /24 RPKI valid
94.176.187.0/24 IPv4 /24 not checked
2a00:ece0::/32 IPv6 /32 RPKI valid
2a04:6c80::/32 IPv6 /32 RPKI valid
2a04:6c81::/32 IPv6 /32 RPKI valid
2a04:6c82::/32 IPv6 /32 not checked
2a04:6c83::/32 IPv6 /32 not checked
2a04:6c84::/32 IPv6 /32 RPKI valid
2a04:6c85::/32 IPv6 /32 RPKI valid
2a04:6c86::/32 IPv6 /32 RPKI valid
2a04:6c87::/32 IPv6 /32 RPKI valid
2a05:1c00::/32 IPv6 /32 RPKI valid
2a05:1c01::/32 IPv6 /32 RPKI valid
2a05:1c02::/32 IPv6 /32 RPKI valid
2a05:1c03::/32 IPv6 /32 RPKI valid
2a05:1c04::/32 IPv6 /32 RPKI valid
2a05:1c05::/32 IPv6 /32 RPKI valid
2a05:1c06::/32 IPv6 /32 not checked
2a05:1c07::/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 AS6718
Address families
Balcan-IX 10,000 Mbps IPv4 · IPv6
NetIX: NetIX — IPv4 · IPv6
RO-IX: Main 10,000 Mbps IPv4 · IPv6
RoNIX 100,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 AS6718 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

19 networks seen before AS6718 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 677 14,487
v4 v6
AS9002 RETN-AS 158 2,810
v4 v6
AS174 COGENT-174 71 1,140
v4 v6
AS57463 NetIX 120 569
v4 v6
AS8708 DIGI-RO 30 510
v4 v6
AS52055 NetIX-Greece 6 46
v4
AS50673 Serverius-as 5 45
v4
AS34019 HIVANE 6 30
v4 v6
AS12310 iNES 3 24
v4
AS39737 Prime-Telecom-AS 3 23
v4 v6
AS34549 MEER-AS 4 17
v4 v6
AS49434 FBWNETWORKS 4 12
v4
AS8298 IPNG 3 10
v4 v6
AS24961 MYLOC-AS 3 9
v4 v6
AS401753 BIXCE 2 8
v4 v6
AS39351 ESAB-AS 2 6
v4
AS48646 STEFAN6 2 2
v6
AS12302 Vodafone_Ro 1 1
v4
AS44682 TFIBER 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS6718 in AS paths

Observed downstreams
Families
AS43431 IX-AS 400 1,899
v4 v6
AS38947 KNETWORKMEDIA 246 319
v4
AS210622 Kicked-SRL 85 111
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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