Skip to main content

AS42760

ABACUS

Abacus Research AG

Registry

Authoritative registration data

AS number
42760
Name
ABACUS
Organisation
Abacus Research AG
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS42760
46.227.224.0/21 IPv4 /21 not checked
77.74.0.0/21 IPv4 /21 not checked
2a02:cd8::/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

Internet Exchange memberships listed for AS42760
Address families
Rheintal IX: Peering-LAN 10,000 Mbps IPv4 · IPv6
SwissIX: Peering 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 AS42760 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS42760 in AS paths

Observed upstreams
Families
AS8758 IWAY 100 307
v4 v6
AS13030 INIT7 77 244
v4 v6
AS6939 HURRICANE 139 209
v4 v6
AS3303 SWISSCOM 58 166
v4 v6
AS34019 HIVANE 4 16
v4 v6
AS39351 ESAB-AS 2 6
v4 v6
AS24961 MYLOC-AS 2 5
v4 v6
AS1764 NEXTLAYER-AS 1 3
v4 v6
AS33891 CORE-BACKBONE 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42760 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

35 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.