Skip to main content

AS44084

MULTIWIRE-AS

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

Registry

Authoritative registration data

AS number
44084
Name
MULTIWIRE-AS
Organisation
------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS44084
217.115.16.0/20 IPv4 /20 not checked
45.67.124.0/22 IPv4 /22 not checked
5.253.212.0/23 IPv4 /23 not checked
2a09:6240::/29 IPv6 /29 RPKI valid
2a09:5dc0::/30 IPv6 /30 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 AS44084
Address families
MIX-IT 20,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 AS44084 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS44084 in AS paths

Observed upstreams
Families
AS12779 ITGATE 725 1,865
v4 v6
AS6939 HURRICANE 87 230
v4 v6
AS8218 NEO-ASN 9 65
v4 v6
AS202709 NETOIP 19 38
v4
AS24482 SGGS-AS-AP 3 32
v4 v6
AS14840 ASN14840 4 30
v4 v6
AS24961 MYLOC-AS 4 12
v4 v6
AS5405 INTERDOTLINK 3 8
v4 v6
AS29075 IELO 3 7
v4 v6
AS4455 BSO 2 6
v4 v6
AS6204 ZET-NET 2 4
v4
AS9498 BBIL-AP 2 4
v4
AS60171 AFRIX-AS 2 4
v4
AS22356 ASN22356 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS44084 in AS paths

Observed downstreams
Families
AS198167 AppToCloud 272 350
v4
AS209387 NEMEXI 244 329
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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