Skip to main content

AS47457

SBERBANK-BALAKOVO-AS

Sberbank of Russia PJSC

Registry

Authoritative registration data

AS number
47457
Name
SBERBANK-BALAKOVO-AS
Organisation
Sberbank of Russia PJSC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS47457
194.54.12.0/24 IPv4 /24 not checked
195.43.144.0/24 IPv4 /24 not checked
91.217.194.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 AS47457 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS47457 in AS paths

Observed upstreams
Families
AS60299 MMTS-AS 63 200
v4
AS35237 Sberbank 61 137
v4
AS9049 ERTH-TRANSIT-AS 21 52
v4
AS8218 NEO-ASN 4 10
v4
AS47692 NESSUS 3 9
v4
AS50673 Serverius-as 3 5
v4
AS6204 ZET-NET 2 3
v4
AS6663 TTI-NET 1 2
v4
AS39351 ESAB-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS47457 in AS paths

Observed downstreams
Families
AS44408 Sber-SMR-AS 7 8
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4
AS200612 GulfBridgeInternational 2 3
v4
AS208972 2 3
v4
AS49673 TRUENETWORK 1 3
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS205112 PHILUNET 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.