Skip to main content

AS43568

VEV-alo1

ORG-RBA3-RIPE

Registry

Authoritative registration data

AS number
43568
Name
VEV-alo1
Organisation
ORG-RBA3-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS43568
77.247.144.0/20 IPv4 /20 not checked
128.0.16.0/21 IPv4 /21 not checked
178.250.216.0/21 IPv4 /21 not checked
185.78.68.0/22 IPv4 /22 not checked
2a02:2470::/29 IPv6 /29 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 AS43568 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS43568 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 185 911
v4 v6
AS50304 BLIX 253 646
v4 v6
AS6939 HURRICANE 26 111
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS43568 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 40
v4
AS28824 ASN-EMPSECURE 1 4
v4
AS34927 iFog-GmbH 1 4
v4
AS57381 FNUTT 1 4
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.