Skip to main content

AS31225

OBLCOM-AS

117393, Moscow, Russia

Registry

Authoritative registration data

AS number
31225
Name
OBLCOM-AS
Organisation
117393, Moscow, Russia
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

0

Total announced

13

Announced prefixes

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

Prefixes announced by AS31225
83.219.229.0/24 IPv4 /24 not checked
83.219.230.0/24 IPv4 /24 not checked
83.219.231.0/24 IPv4 /24 not checked
83.219.232.0/24 IPv4 /24 not checked
83.219.233.0/24 IPv4 /24 not checked
83.219.235.0/24 IPv4 /24 not checked
83.219.238.0/24 IPv4 /24 not checked
83.219.239.0/24 IPv4 /24 not checked
83.219.240.0/24 IPv4 /24 not checked
83.219.241.0/24 IPv4 /24 not checked
83.219.242.0/24 IPv4 /24 not checked
83.219.246.0/24 IPv4 /24 not checked
83.219.247.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 AS31225 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS31225 in AS paths

Observed upstreams
Families
AS50254 sky-en 330 4,118
v4
AS12389 274 727
v4
AS25091 IP-Max 4 56
v4
AS137409 GSLNETWORKS-AS-AP 2 21
v4
AS9198 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS31225 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 35
v4
AS29049 1 7
v4
AS37721 ORG-VTS1-AFRINIC 1 7
v4
AS49434 1 7
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.