Skip to main content

AS402960

MACWEB

Registry

Authoritative registration data

AS number
402960
Name
MACWEB
Organisation
MACWEB
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS402960
207.186.80.0/20 IPv4 /20 not checked
2604:acc0::/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 AS402960
Address families
Any2West 100,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 AS402960 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS402960 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 249 499
v4 v6
AS6939 HURRICANE 94 139
v4 v6
AS6057 6057 2 2
v4
AS7575 AARNET-AS-AP 1 1
v4
AS137409 GSLNETWORKS-AS-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS402960 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 11
v4
AS49544 i3Dnet 1 2
v4
AS1828 UNITAS 1 1
v4
AS17639 CONVERGE-AS 1 1
v4
AS36236 NETACTUATE 1 1
v4
AS45489 SLT-GLOBAL 1 1
v4
AS51185 MAINSTREAMING-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.