Skip to main content

AS48366

Inforoom

Inforoom Ltd.

Registry

Authoritative registration data

AS number
48366
Name
Inforoom
Organisation
Inforoom Ltd.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS48366
91.219.4.0/22 IPv4 /22 not checked
91.235.88.0/22 IPv4 /22 not checked
91.209.124.0/24 IPv4 /24 not checked
91.229.177.0/24 IPv4 /24 not checked
91.235.88.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

Internet Exchange memberships listed for AS48366
Address families
MSK-IX Moscow: MSK-IX peering network 5,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 AS48366 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS48366 in AS paths

Observed upstreams
Families
AS57304 RETNRU-AS 154 548
v4
AS58002 SINFORM 52 122
v4
AS9002 RETN-AS 6 14
v4
AS25091 IP-Max 4 14
v4
AS8732 COMCOR-AS 1 1
v4
AS13194 BITE 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS48366 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 13
v4
AS49673 TRUENETWORK 3 4
v4
AS34927 iFog-GmbH 1 4
v4
AS37721 ORG-VTS1-AFRINIC 1 3
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.