Skip to main content

AS42532

VEESP-LV-AS

SIA VEESP

Registry

Authoritative registration data

AS number
42532
Name
VEESP-LV-AS
Organisation
SIA VEESP
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

32

IPv6 prefixes

7

Total announced

39

Announced prefixes

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

Prefixes announced by AS42532
13.140.0.0/21 IPv4 /21 not checked
13.140.16.0/21 IPv4 /21 not checked
13.140.8.0/21 IPv4 /21 not checked
169.40.0.0/21 IPv4 /21 not checked
178.173.248.0/21 IPv4 /21 not checked
188.253.16.0/21 IPv4 /21 not checked
5.34.208.0/21 IPv4 /21 not checked
62.182.192.0/21 IPv4 /21 not checked
185.22.172.0/22 IPv4 /22 not checked
185.242.104.0/22 IPv4 /22 not checked
188.253.24.0/22 IPv4 /22 not checked
195.135.252.0/22 IPv4 /22 not checked
216.173.68.0/22 IPv4 /22 not checked
37.128.204.0/22 IPv4 /22 not checked
45.43.76.0/22 IPv4 /22 not checked
46.32.184.0/22 IPv4 /22 not checked
82.115.4.0/22 IPv4 /22 not checked
91.197.0.0/22 IPv4 /22 not checked
94.126.228.0/22 IPv4 /22 not checked
94.242.58.0/23 IPv4 /23 not checked
185.145.245.0/24 IPv4 /24 not checked
185.155.119.0/24 IPv4 /24 not checked
212.6.44.0/24 IPv4 /24 not checked
62.182.197.0/24 IPv4 /24 not checked
62.182.198.0/24 IPv4 /24 not checked
62.182.199.0/24 IPv4 /24 not checked
77.73.71.0/24 IPv4 /24 not checked
94.158.218.0/24 IPv4 /24 not checked
94.158.219.0/24 IPv4 /24 not checked
94.242.48.0/24 IPv4 /24 not checked
94.242.49.0/24 IPv4 /24 not checked
94.242.63.0/24 IPv4 /24 not checked
2a0c:16c0::/32 IPv6 /32 not checked
2a0c:16c1::/32 IPv6 /32 not checked
2a0c:16c2::/32 IPv6 /32 not checked
2a0c:16c3::/32 IPv6 /32 not checked
2a0c:16c4::/32 IPv6 /32 not checked
2a11:8100::/32 IPv6 /32 not checked
2a00:1838:9100::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS42532 in AS paths

Observed upstreams
Families
AS9002 3,646 16,974
v4 v6
AS1299 1,395 4,552
v4 v6
AS6939 457 1,784
v4 v6
AS33891 129 607
v4 v6
AS3303 133 556
v4 v6
AS35280 94 367
v4 v6
AS5405 75 330
v4 v6
AS20764 69 291
v4 v6
AS50304 53 223
v4 v6
AS4455 36 195
v4
AS39351 36 143
v4 v6
AS20485 21 70
v4
AS14840 10 65
v6
AS25091 8 36
v4
AS13194 7 14
v4
AS20473 5 13
v6
AS12389 4 9
v4 v6
AS12552 1 6
v4
AS52005 1 6
v4
AS24961 2 2
v6
AS34927 2 2
v6
AS50629 2 2
v6
AS6663 1 1
v6
AS56655 1 1
v6

No rows match “”.

Showing of

Observed downstreams

17 networks seen after AS42532 in AS paths

Observed downstreams
Families
AS209183 452 4,562
v4 v6
AS219443 449 1,364
v4 v6
AS205290 299 1,349
v4
AS199742 439 1,032
v4 v6
AS206715 419 1,019
v4 v6
AS216253 405 1,013
v4
AS59615 459 692
v4 v6
AS210751 403 673
v4
AS207359 266 672
v4
AS203614 265 672
v4
AS206787 267 338
v4
AS210502 267 338
v4
AS205261 266 338
v4
AS200328 266 336
v4
AS219335 265 336
v4
AS198130 264 336
v4
AS213164 264 335
v4

No rows match “”.

Showing of

Uncertain adjacencies

36 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 18 744
v4 v6
AS49544 18 156
v4 v6
AS28917 16 81
v4 v6
AS36236 18 79
v4 v6
AS42473 18 78
v4 v6
AS42541 18 78
v4 v6
AS199524 18 78
v4 v6
AS205206 18 78
v4 v6
AS35598 16 63
v4
AS3399 14 53
v4 v6
AS1257 16 52
v4 v6
AS21412 16 50
v4
AS212483 5 26
v6
AS209183 1 14
v4 v6
AS51519 5 13
v6
AS198150 5 13
v6
AS205290 1 4
v4
AS219443 1 4
v4 v6
AS199742 1 3
v4 v6
AS206715 1 3
v4 v6
AS216253 1 3
v4
AS12859 1 2
v6
AS203614 1 2
v4
AS207359 1 2
v4
AS210751 1 2
v4
AS39122 1 1
v6
AS41327 1 1
v6
AS59615 1 1
v4
AS198130 1 1
v4
AS200328 1 1
v4
AS205261 1 1
v4
AS206787 1 1
v4
AS209823 1 1
v6
AS210502 1 1
v4
AS213164 1 1
v4
AS219335 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.