Skip to main content

AS29600

LATVENERGO-AS

Ventspils street 58, LV-1046

Registry

Authoritative registration data

AS number
29600
Name
LATVENERGO-AS
Organisation
Ventspils street 58, LV-1046
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS29600
85.15.192.0/18 IPv4 /18 RPKI valid
80.70.16.0/20 IPv4 /20 not checked
83.136.136.0/21 IPv4 /21 not checked
95.131.112.0/21 IPv4 /21 RPKI valid
80.70.24.0/23 IPv4 /23 RPKI valid
80.70.19.0/24 IPv4 /24 not checked
80.70.28.0/24 IPv4 /24 RPKI valid
80.70.29.0/24 IPv4 /24 RPKI valid
83.136.136.0/24 IPv4 /24 RPKI valid
85.15.193.0/24 IPv4 /24 RPKI valid
2a01:a880::/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 AS29600 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS29600 in AS paths

Observed upstreams
Families
AS13194 BITE 1,207 5,115
v4 v6
AS6939 HURRICANE 159 390
v4 v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS29600 in AS paths

Observed downstreams
Families
AS42936 SPX 390 691
v4 v6
AS35302 Latvenergo-AS-2 278 690
v4
AS28699 Unistar-AS 276 344
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28917 Fiord-AS 4 18
v4 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.