Skip to main content

AS201986

Arpinet

============================

Registry

Authoritative registration data

AS number
201986
Name
Arpinet
Organisation
============================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS201986
178.219.56.0/21 IPv4 /21 not checked
185.150.164.0/22 IPv4 /22 not checked
185.57.68.0/22 IPv4 /22 not checked
194.61.88.0/22 IPv4 /22 not checked
178.219.58.0/23 IPv4 /23 not checked
185.150.164.0/23 IPv4 /23 not checked
45.153.212.0/23 IPv4 /23 not checked
45.153.214.0/23 IPv4 /23 not checked
109.68.127.0/24 IPv4 /24 not checked
185.150.167.0/24 IPv4 /24 not checked
194.61.90.0/24 IPv4 /24 not checked
2a02:5960::/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 AS201986
Address families
ArmIX: Peering 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 AS201986 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS201986 in AS paths

Observed upstreams
Families
AS8932 UCOMINT 3,102 8,019
v4 v6
AS12297 2,310 6,519
v4 v6

No rows match “”.

Showing – of

Observed downstreams

14 networks seen after AS201986 in AS paths

Observed downstreams
Families
AS207980 611 1,411
v4 v6
AS200896 341 1,406
v4
AS8226 339 1,106
v4
AS207991 447 1,072
v4 v6
AS214977 558 1,062
v4 v6
AS205277 282 1,053
v4
AS210315 285 1,050
v4
AS12297 309 390
v4
AS34083 285 351
v4
AS197805 284 350
v4
AS211944 282 350
v4
AS218847 263 341
v4
AS209778 242 309
v4
AS8932 UCOMINT 52 62
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS200896 1 4
v4
AS8226 2 2
v4
AS34083 1 1
v4

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.