Skip to main content

AS207133

RUCOMTECH-AS

Moscow, Russia

Registry

Authoritative registration data

AS number
207133
Name
RUCOMTECH-AS
Organisation
Moscow, Russia
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS207133
185.160.216.0/22 IPv4 /22 not checked
185.250.48.0/22 IPv4 /22 not checked
2a0c:78c0::/29 IPv6 /29 not checked
2a04:2bc0::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS207133 in AS paths

Observed upstreams
Families
AS20764 RASCOM-AS 370 1,051
v4 v6
AS35598 131 272
v4 v6
AS1299 TWELVE99 74 215
v4 v6
AS9049 29 92
v4 v6
AS62255 BEMYLINK 25 72
v4 v6
AS25478 15 34
v4 v6
AS25091 IP-Max 8 33
v4 v6
AS50384 W-IX_LTD 5 9
v4 v6
AS9198 1 2
v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS207133 in AS paths

Observed downstreams
Families
AS211773 235 312
v4
AS201498 13 18
v4

No rows match “”.

Showing of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 15
v4 v6
AS49544 i3Dnet 2 6
v4
AS36236 NETACTUATE 2 5
v4 v6
AS41327 FIBERTELECOM-AS 2 5
v4 v6
AS41722 2 5
v4 v6
AS49673 TRUENETWORK 2 3
v4
AS199524 GCORE 2 3
v4
AS28910 1 2
v6

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.