Skip to main content

AS31617

REEVO

--------------------------------------------------------------------------

Registry

Authoritative registration data

AS number
31617
Name
REEVO
Organisation
--------------------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

2

Total announced

20

Announced prefixes

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

Prefixes announced by AS31617
151.1.100.0/22 IPv4 /22 not checked
185.186.92.0/22 IPv4 /22 not checked
185.252.52.0/22 IPv4 /22 not checked
217.26.180.0/22 IPv4 /22 not checked
45.66.100.0/22 IPv4 /22 not checked
45.92.148.0/22 IPv4 /22 not checked
62.192.148.0/22 IPv4 /22 not checked
194.143.142.0/23 IPv4 /23 not checked
195.88.230.0/23 IPv4 /23 not checked
195.88.234.0/23 IPv4 /23 not checked
91.241.86.0/23 IPv4 /23 not checked
151.1.100.0/24 IPv4 /24 not checked
185.252.52.0/24 IPv4 /24 not checked
192.166.252.0/24 IPv4 /24 not checked
192.172.232.0/24 IPv4 /24 not checked
192.188.248.0/24 IPv4 /24 not checked
192.207.14.0/24 IPv4 /24 not checked
193.23.114.0/24 IPv4 /24 not checked
2a0b:7380::/29 IPv6 /29 RPKI valid
2a0c:2140::/29 IPv6 /29 RPKI valid

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 AS31617
Address families
MIX-IT 10,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS31617 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS31617 in AS paths

Observed downstreams
Families
AS209191 MEDIATECH 227 273
v4

No rows match “”.

Showing – of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

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.