Skip to main content

AS49870

AS49870-BV

Alsycon B.V.

Registry

Authoritative registration data

AS number
49870
Name
AS49870-BV
Organisation
Alsycon B.V.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

24

IPv6 prefixes

1

Total announced

25

Announced prefixes

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

Prefixes announced by AS49870
160.119.64.0/22 IPv4 /22 not checked
196.61.64.0/22 IPv4 /22 not checked
160.119.76.0/23 IPv4 /23 not checked
45.140.222.0/23 IPv4 /23 not checked
45.80.36.0/23 IPv4 /23 not checked
45.81.22.0/23 IPv4 /23 not checked
45.95.144.0/23 IPv4 /23 not checked
160.119.69.0/24 IPv4 /24 not checked
160.119.71.0/24 IPv4 /24 not checked
160.119.74.0/24 IPv4 /24 not checked
160.119.75.0/24 IPv4 /24 not checked
160.119.78.0/24 IPv4 /24 not checked
169.239.130.0/24 IPv4 /24 not checked
185.142.130.0/24 IPv4 /24 not checked
185.224.128.0/24 IPv4 /24 not checked
194.50.16.0/24 IPv4 /24 not checked
2.56.167.0/24 IPv4 /24 not checked
212.107.12.0/24 IPv4 /24 not checked
45.95.146.0/24 IPv4 /24 not checked
45.95.147.0/24 IPv4 /24 not checked
77.83.240.0/24 IPv4 /24 not checked
89.116.202.0/24 IPv4 /24 not checked
89.190.156.0/24 IPv4 /24 not checked
89.190.159.0/24 IPv4 /24 not checked
2a0e:3980::/29 IPv6 /29 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS49870 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

35 networks seen before AS49870 in AS paths

Observed upstreams
Families
AS174 588 4,296
v4 v6
AS57717 460 2,402
v4
AS3257 261 2,325
v4 v6
AS6939 813 1,312
v4 v6
AS9002 241 605
v4
AS13194 143 372
v4
AS14840 7 120
v4
AS25091 9 71
v4 v6
AS3214 9 68
v4 v6
AS34019 13 56
v4 v6
AS3303 19 48
v4
AS5405 17 48
v4 v6
AS61049 8 45
v4
AS8298 12 42
v4 v6
AS39351 12 42
v4 v6
AS20764 13 41
v4
AS41441 2 40
v4
AS34927 7 34
v4
AS1103 11 33
v4 v6
AS137409 7 33
v4
AS286 5 30
v4 v6
AS50869 4 28
v4
AS50629 11 25
v4 v6
AS58057 3 22
v4 v6
AS56911 6 16
v4
AS29075 6 14
v4 v6
AS62000 5 12
v4 v6
AS6204 3 8
v4
AS20766 3 8
v4
AS41051 4 4
v6
AS9498 2 4
v4
AS39686 2 4
v4
AS50673 2 2
v6
AS9044 1 2
v6
AS22356 1 2
v4

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS49870 in AS paths

Observed downstreams
Families
AS49305 466 1,730
v4 v6
AS7489 454 1,031
v4 v6
AS209101 266 674
v4
AS51942 62 497
v4
AS208911 256 362
v6

No rows match “”.

Showing of

Uncertain adjacencies

24 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 6 191
v4 v6
AS49544 6 42
v4 v6
AS212483 4 36
v4
AS39122 6 32
v4 v6
AS198150 4 28
v4
AS271253 4 28
v4
AS12859 6 25
v4 v6
AS3399 6 21
v4 v6
AS6424 6 21
v4 v6
AS58299 6 21
v4 v6
AS209823 6 21
v4 v6
AS62167 2 20
v4 v6
AS44901 1 20
v4
AS202365 1 20
v4
AS37721 4 17
v4
AS199524 4 17
v4
AS28917 2 12
v4
AS29049 3 8
v4
AS263152 3 8
v4
AS1257 1 3
v4
AS21412 1 3
v4
AS24961 1 1
v6
AS41327 1 1
v6
AS56662 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.