Skip to main content

AS39046

THEOREMA

St. Petersburg, Russian Federation

Registry

Authoritative registration data

AS number
39046
Name
THEOREMA
Organisation
St. Petersburg, Russian Federation
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS39046
80.254.48.0/20 IPv4 /20 not checked
185.77.8.0/23 IPv4 /23 not checked
185.77.10.0/24 IPv4 /24 not checked
80.254.52.0/24 IPv4 /24 not checked
80.254.54.0/24 IPv4 /24 not checked
80.254.56.0/24 IPv4 /24 not checked
80.254.58.0/24 IPv4 /24 not checked
80.254.61.0/24 IPv4 /24 not checked
2a03:51a0::/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 AS39046
Address families
CLOUD-IX SPB 10,000 Mbps IPv4
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS39046 in AS paths

Observed upstreams
Families
AS3216 SOVAM-AS 272 1,841
v4 v6
AS35598 107 414
v4
AS29076 106 203
v4 v6
AS31500 60 200
v4 v6
AS9002 RETN-AS 91 198
v4 v6
AS1299 TWELVE99 41 153
v4 v6
AS62255 BEMYLINK 17 57
v4
AS57304 20 29
v4 v6
AS47692 2 14
v4 v6
AS6663 1 4
v4 v6
AS60171 1 4
v4 v6
AS6204 1 3
v4
AS9198 1 3
v4
AS15958 1 3
v4
AS42295 TBISS-AS 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS39046 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

19 adjacencies that may be an artefact of collector peering

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.