Skip to main content

AS48894

OPTIMUS-AS

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

Registry

Authoritative registration data

AS number
48894
Name
OPTIMUS-AS
Organisation
--------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

3

Total announced

17

Announced prefixes

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

Prefixes announced by AS48894
152.89.232.0/23 IPv4 /23 RPKI valid
152.89.234.0/24 IPv4 /24 RPKI valid
152.89.235.0/24 IPv4 /24 not checked
188.190.0.0/24 IPv4 /24 not checked
192.71.244.0/24 IPv4 /24 RPKI valid
193.104.240.0/24 IPv4 /24 not checked
193.9.21.0/24 IPv4 /24 not checked
195.206.228.0/24 IPv4 /24 RPKI valid
195.206.229.0/24 IPv4 /24 not checked
86.54.86.0/24 IPv4 /24 RPKI valid
91.132.94.0/24 IPv4 /24 not checked
91.223.182.0/24 IPv4 /24 not checked
91.226.99.0/24 IPv4 /24 not checked
91.240.216.0/24 IPv4 /24 RPKI valid
2a09:37c0::/29 IPv6 /29 RPKI valid
2001:67c:2468::/48 IPv6 /48 not checked
2a03:f80:386::/48 IPv6 /48 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS48894 in AS paths

Observed upstreams
Families
AS21283 A1SI-AS 376 3,638
v4 v6
AS56635 XENYA 109 1,688
v4
AS6939 HURRICANE 28 30
v4
AS14840 ASN14840 2 5
v4
AS9498 BBIL-AP 1 1
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS48894 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS3212 TELEMACH 1 5
v4 v6
AS198150 SIACOM-AS 1 1
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.