Skip to main content

AS20848

ROSBUSINESSCONSULTING-AS

ROSBUSINESSCONSULTING JSC

Registry

Authoritative registration data

AS number
20848
Name
ROSBUSINESSCONSULTING-AS
Organisation
ROSBUSINESSCONSULTING JSC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

0

Total announced

14

Announced prefixes

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

Prefixes announced by AS20848
80.68.240.0/20 IPv4 /20 not checked
185.72.228.0/22 IPv4 /22 not checked
80.68.240.0/22 IPv4 /22 not checked
80.68.248.0/22 IPv4 /22 not checked
80.68.246.0/23 IPv4 /23 not checked
80.68.250.0/23 IPv4 /23 not checked
185.134.204.0/24 IPv4 /24 not checked
185.134.205.0/24 IPv4 /24 not checked
185.134.207.0/24 IPv4 /24 not checked
185.72.228.0/24 IPv4 /24 not checked
80.68.244.0/24 IPv4 /24 not checked
80.68.252.0/24 IPv4 /24 not checked
80.68.253.0/24 IPv4 /24 not checked
80.68.255.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 AS20848 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS20848 in AS paths

Observed upstreams
Families
AS201706 285 2,354
v4
AS31133 MF-MGSM-AS 223 1,148
v4
AS199599 CIREX 197 722
v4
AS8359 MTS 103 452
v4
AS3216 SOVAM-AS 45 212
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS20848 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35598 INETCOM 1 10
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.