Skip to main content

AS203473

LOGINNET-AS

Servis Svyazi LOGINNET llc

Registry

Authoritative registration data

AS number
203473
Name
LOGINNET-AS
Organisation
Servis Svyazi LOGINNET llc
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS203473
45.8.231.0/24 IPv4 /24 not checked
91.215.202.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 AS203473 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS203473 in AS paths

Observed upstreams
Families
AS31277 NEWLINE-AS 289 738
v4
AS25091 IP-Max 4 16
v4
AS137409 GSLNETWORKS-AS-AP 1 4
v4
AS9198 KAZTELECOM-AS 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS203473 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 10
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS41722 MIRAN-AS 1 2
v4
AS49434 FBWNETWORKS 1 2
v4
AS205112 PHILUNET 1 2
v4
AS209823 ENKI-AS 1 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.