Skip to main content

AS43317

VEESP-AS

SIA VEESP

Registry

Authoritative registration data

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

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS43317
94.242.48.0/20 IPv4 /20 not checked
77.73.64.0/21 IPv4 /21 not checked
94.242.0.0/23 IPv4 /23 not checked
91.209.70.0/24 IPv4 /24 not checked
2a00:1838::/32 IPv6 /32 not checked
2a0a:4784::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS43317 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS43317 in AS paths

Observed upstreams
Families
AS20764 RASCOM-AS 771 1,832
v4 v6
AS31500 337 922
v4 v6
AS6939 HURRICANE 149 309
v4 v6
AS47692 NESSUS 4 17
v4 v6
AS41327 FIBERTELECOM-AS 4 11
v4 v6
AS15958 3 5
v4
AS60171 AFRIX-AS 1 4
v4 v6
AS42532 VEESP-LV-AS 2 3
v4
AS50673 Serverius-as 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS43317 in AS paths

Observed downstreams
Families
AS59615 SERVERUM-AS 431 705
v4 v6
AS206787 OSV 264 342
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37721 ORG-VTS1-AFRINIC 3 11
v4 v6
AS44901 belcloud 3 8
v4 v6
AS209823 2 7
v4 v6
AS13004 3 5
v4
AS35598 3 5
v4
AS200612 GulfBridgeInternational 3 5
v4
AS208972 3 5
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.