Skip to main content

AS34312

ARMNET-AS

------------------------------------------------------------

Registry

Authoritative registration data

AS number
34312
Name
ARMNET-AS
Organisation
------------------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS34312
89.200.248.0/21 IPv4 /21 not checked
193.111.6.0/23 IPv4 /23 not checked
195.95.206.0/24 IPv4 /24 not checked
195.95.207.0/24 IPv4 /24 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 AS34312 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS34312 in AS paths

Observed upstreams
Families
AS3326 Datagroup 505 1,178
v4
AS57455 207 407
v4
AS28917 Fiord-AS 86 115
v4
AS6939 HURRICANE 40 62
v4
AS42504 UKRBIT-NET-AS 10 11
v4
AS3303 SWISSCOM 8 10
v4
AS14840 ASN14840 4 10
v4
AS6663 TTI-NET 1 1
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS34312 in AS paths

Observed downstreams
Families
AS20971 272 367
v4

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 8
v4
AS48919 UA-CITY-AS 2 4
v4
AS59514 DARNYTSIA-NET 2 4
v4
AS212483 level86 2 4
v4
AS198150 SIACOM-AS 2 2
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.