Skip to main content

AS207353

Ruform

Ruform LLC

Registry

Authoritative registration data

AS number
207353
Name
Ruform
Organisation
Ruform LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS207353
185.62.100.0/24 IPv4 /24 not checked
195.246.246.0/24 IPv4 /24 not checked
31.184.228.0/24 IPv4 /24 not checked
31.184.229.0/24 IPv4 /24 not checked
46.161.43.0/24 IPv4 /24 not checked
5.189.216.0/24 IPv4 /24 not checked
77.220.216.0/24 IPv4 /24 not checked
77.220.218.0/24 IPv4 /24 not checked
77.220.220.0/24 IPv4 /24 not checked
77.220.221.0/24 IPv4 /24 not checked
77.220.223.0/24 IPv4 /24 not checked
89.248.230.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 AS207353
Address families
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 AS207353 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS207353 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207353 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS35598 INETCOM 1 7
v4
AS28910 INTAL-ASN 1 6
v4
AS36236 NETACTUATE 1 6
v4
AS41722 MIRAN-AS 1 6
v4
AS49673 TRUENETWORK 1 6
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.