Skip to main content

AS41720

NAVIGABENE

Contact: noc@as41720.net

Registry

Authoritative registration data

AS number
41720
Name
NAVIGABENE
Organisation
Contact: noc@as41720.net
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

5

Total announced

19

Announced prefixes

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

Prefixes announced by AS41720
103.188.231.0/24 IPv4 /24 not checked
185.130.88.0/24 IPv4 /24 not checked
185.21.129.0/24 IPv4 /24 not checked
185.225.6.0/24 IPv4 /24 not checked
185.242.180.0/24 IPv4 /24 not checked
185.242.181.0/24 IPv4 /24 not checked
185.242.182.0/24 IPv4 /24 not checked
185.242.183.0/24 IPv4 /24 not checked
195.182.210.0/24 IPv4 /24 not checked
195.182.211.0/24 IPv4 /24 not checked
45.146.5.0/24 IPv4 /24 not checked
5.178.124.0/24 IPv4 /24 not checked
5.178.125.0/24 IPv4 /24 not checked
5.182.48.0/24 IPv4 /24 not checked
2a0d:8c00::/29 IPv6 /29 not checked
2a0d:b280::/29 IPv6 /29 not checked
2001:67c:d68::/48 IPv6 /48 not checked
2a0d:b280:8100::/48 IPv6 /48 not checked
2a10:fa81:1001::/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 AS41720
Address families
INTERIX 1,000 Mbps IPv4 · IPv6
MINAP Milan: MINAP 40,000 Mbps IPv4 · IPv6
MIX-IT 20,000 Mbps IPv4 · IPv6
PCIX 10,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 AS41720 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

22 networks seen before AS41720 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 2,021 4,960
v4 v6
AS60798 594 3,307
v4
AS174 COGENT-174 1,137 3,114
v4 v6
AS216309 335 1,996
v4 v6
AS6939 HURRICANE 567 1,602
v4 v6
AS8218 NEO-ASN 58 514
v4 v6
AS13030 INIT7 69 438
v4 v6
AS1299 TWELVE99 137 405
v4 v6
AS24482 SGGS-AS-AP 20 392
v4 v6
AS14840 ASN14840 32 300
v4 v6
AS5405 44 174
v4 v6
AS137409 GSLNETWORKS-AS-AP 25 80
v4 v6
AS4455 12 45
v4 v6
AS22356 9 41
v4 v6
AS28716 13 39
v6
AS6204 8 30
v4
AS29632 18 28
v6
AS60171 5 21
v4
AS9009 M247 4 19
v4
AS31543 4 12
v4 v6
AS9498 2 8
v4
AS263444 2 8
v4

No rows match “”.

Showing of

Observed downstreams

22 networks seen after AS41720 in AS paths

Observed downstreams
Families
AS208328 491 2,093
v4 v6
AS47152 667 1,964
v4 v6
AS58180 405 1,263
v4 v6
AS9002 RETN-AS 192 1,121
v4 v6
AS202704 366 1,055
v4 v6
AS215760 420 1,016
v4 v6
AS60798 123 811
v4
AS216309 447 643
v4 v6
AS212751 131 450
v4 v6
AS213709 255 353
v6
AS215146 254 350
v6
AS198747 252 350
v6
AS212467 247 346
v6
AS21429 236 309
v4
AS208437 12 39
v4 v6
AS1299 TWELVE99 11 39
v4 v6
AS208753 24 31
v6
AS174 COGENT-174 1 6
v4
AS39657 1 4
v4
AS201333 2 2
v4
AS6517 1 1
v4
AS15169 GOOGLE 1 1
v6

No rows match “”.

Showing of

Uncertain adjacencies

31 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS12779 ITGATE 17 179
v4 v6
AS51185 MAINSTREAMING-AS 28 152
v4 v6
AS212483 level86 16 120
v4 v6
AS49544 i3Dnet 19 118
v4 v6
AS20912 19 63
v4 v6
AS49605 17 62
v4 v6
AS50877 17 62
v4 v6
AS57111 17 62
v4 v6
AS12637 17 60
v4 v6
AS198150 16 60
v4 v6
AS5394 Unidata 16 57
v4 v6
AS15605 17 52
v4 v6
AS47152 6 26
v4 v6
AS13237 9 25
v4
AS202032 9 25
v4
AS8660 MATRIX-AS 8 24
v4
AS29049 6 22
v4
AS5392 TELNET-ITALY 6 21
v4
AS20811 BRENNERCOM-AS 5 20
v4
AS59919 5 20
v4
AS58180 1 4
v4 v6
AS202704 1 4
v4 v6
AS208328 1 4
v6
AS215760 1 3
v4 v6
AS21429 1 1
v4
AS198747 1 1
v6
AS208437 1 1
v4
AS208753 1 1
v6
AS212467 1 1
v6
AS213709 1 1
v6
AS215146 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.