Skip to main content

AS42687

IzarLink1

-------------------------------------

Registry

Authoritative registration data

AS number
42687
Name
IzarLink1
Organisation
-------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS42687
161.104.8.0/21 IPv4 /21 RPKI valid
185.182.168.0/22 IPv4 /22 RPKI valid
185.203.176.0/22 IPv4 /22 RPKI valid
193.142.128.0/22 IPv4 /22 not checked
185.219.240.0/23 IPv4 /23 RPKI not found
185.219.242.0/23 IPv4 /23 RPKI valid
185.203.177.0/24 IPv4 /24 not checked
185.217.141.0/24 IPv4 /24 RPKI valid
2a0d:25c0::/29 IPv6 /29 RPKI valid

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 AS42687
Address families
BéarnIX 1,000 Mbps IPv4 · IPv6
France-IX Paris 2,000 Mbps IPv4 · IPv6
nine 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 AS42687 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS42687 in AS paths

Observed upstreams
Families
AS35280 F5 198 1,446
v4 v6
AS201675 SACLAK-NETWORK 321 813
v4 v6
AS6939 HURRICANE 46 137
v4 v6
AS25091 IP-Max 2 23
v4 v6
AS5405 INTERDOTLINK 2 11
v4 v6
AS34177 CELESTE-AS 2 11
v4 v6
AS6057 6057 2 10
v4
AS29075 IELO 2 7
v4 v6
AS8218 NEO-ASN 2 6
v6
AS4455 BSO 1 6
v4 v6
AS6758 AS6758 1 6
v4 v6
AS60171 AFRIX-AS 1 6
v4 v6
AS215596 Kissgroup 1 6
v4 v6
AS6204 ZET-NET 1 5
v4
AS6696 VERIXI 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42687 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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