Skip to main content

AS12847

LMT-NET

Riga, Latvia

Registry

Authoritative registration data

AS number
12847
Name
LMT-NET
Organisation
Riga, Latvia
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 AS12847
212.93.96.0/19 IPv4 /19 RPKI valid
212.93.124.0/23 IPv4 /23 RPKI valid
194.125.240.0/24 IPv4 /24 RPKI valid
212.93.126.0/24 IPv4 /24 RPKI valid
2a03:ec00::/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

Internet Exchange memberships listed for AS12847
Address families
BALT-IX: BALT-IX 20,000 Mbps IPv4 · IPv6
GLV-IX 200,000 Mbps IPv4 · IPv6
SMILE-IXP: VLAN333 200,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

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

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS12847 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 1,006 11,372
v4 v6
AS1299 TWELVE99 222 3,802
v4 v6
AS13194 BITE 371 2,804
v4 v6
AS12578 APOLLO-AS 226 1,575
v4 v6
AS55002 DEFENSE-NET 264 710
v4
AS174 COGENT-174 106 599
v4 v6
AS3303 SWISSCOM 23 466
v4 v6
AS1257 SWIPNET 6 100
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS12847 in AS paths

Observed downstreams
Families
AS24921 LMT-3G 1,691 19,587
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS21412 CGATES-AS 3 47
v4
AS28917 Fiord-AS 3 11
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.