Skip to main content

AS40138

MDNET

Mach Dilemma, LLC

Registry

Authoritative registration data

AS number
40138
Name
MDNET
Organisation
Mach Dilemma, LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

39

Total announced

51

Announced prefixes

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

Prefixes announced by AS40138
103.196.36.0/23 IPv4 /23 RPKI valid
45.127.112.0/23 IPv4 /23 not checked
103.196.36.0/24 IPv4 /24 not checked
103.196.37.0/24 IPv4 /24 not checked
103.196.38.0/24 IPv4 /24 RPKI valid
198.72.6.0/24 IPv4 /24 RPKI valid
44.30.92.0/24 IPv4 /24 not checked
44.31.181.0/24 IPv4 /24 not checked
45.127.112.0/24 IPv4 /24 RPKI valid
45.127.113.0/24 IPv4 /24 RPKI valid
45.127.114.0/24 IPv4 /24 not checked
45.127.115.0/24 IPv4 /24 RPKI valid
2620:95:4000::/46 IPv6 /46 RPKI valid
2402:e580:73e9::/48 IPv6 /48 RPKI valid
2402:e580:73ea::/48 IPv6 /48 RPKI valid
2402:e580:73eb::/48 IPv6 /48 RPKI valid
2402:e580:73ee::/48 IPv6 /48 not checked
2402:e580:73ef::/48 IPv6 /48 not checked
2402:e580:73f0::/48 IPv6 /48 RPKI valid
2402:e580:73f1::/48 IPv6 /48 RPKI valid
2402:e580:73f2::/48 IPv6 /48 not checked
2402:e580:73f3::/48 IPv6 /48 RPKI valid
2402:e580:73f6::/48 IPv6 /48 RPKI valid
2402:e580:73f7::/48 IPv6 /48 RPKI valid
2402:e580:73f8::/48 IPv6 /48 RPKI valid
2402:e580:73f9::/48 IPv6 /48 RPKI valid
2402:e580:744d::/48 IPv6 /48 RPKI valid
2402:e580:744e::/48 IPv6 /48 RPKI valid
2402:e580:744f::/48 IPv6 /48 RPKI valid
2402:e580:7450::/48 IPv6 /48 RPKI valid
2402:e580:7451::/48 IPv6 /48 RPKI valid
2402:e580:7452::/48 IPv6 /48 RPKI valid
2402:e580:7453::/48 IPv6 /48 RPKI valid
2402:e580:7456::/48 IPv6 /48 RPKI valid
2402:e580:745a::/48 IPv6 /48 not checked
2402:e580:74b1::/48 IPv6 /48 not checked
2402:e580:74b2::/48 IPv6 /48 RPKI valid
2402:e580:74b3::/48 IPv6 /48 RPKI valid
2402:e580:74b5::/48 IPv6 /48 RPKI valid
2402:e580:74b6::/48 IPv6 /48 not checked
2402:e580:74b7::/48 IPv6 /48 not checked
2402:e580:74b8::/48 IPv6 /48 RPKI valid
2402:e580:74b9::/48 IPv6 /48 RPKI valid
2402:e580:74ba::/48 IPv6 /48 RPKI valid
2402:e580:77d3::/48 IPv6 /48 RPKI valid
2402:e580:77d7::/48 IPv6 /48 RPKI valid
2402:e580:77de::/48 IPv6 /48 not checked
2402:e580:7836::/48 IPv6 /48 RPKI valid
2620:95:4001::/48 IPv6 /48 RPKI valid
2620:95:4002::/48 IPv6 /48 RPKI valid
2620:95:4007::/48 IPv6 /48 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 AS40138
Address families
FCIX 10,000 Mbps IPv4 · IPv6
KCIX 10,000 Mbps IPv4 · IPv6
MegaIX Bay Area — IPv4 · IPv6
SIX Seattle: MTU 1500 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 AS40138 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS40138 in AS paths

Observed upstreams
Families
AS20473 AS-VULTR 1,421 6,167
v4 v6
AS6939 HURRICANE 173 933
v4 v6
AS36236 NETACTUATE 281 594
v4 v6
AS47787 EDGOO 13 48
v4 v6
AS394256 CLOUDSINGULARITY 1 4
v4
AS58057 SECUREBIT 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS40138 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 15
v4 v6
AS9002 RETN-AS 1 5
v4 v6
AS49544 i3Dnet 1 5
v4 v6
AS35280 F5 1 4
v4
AS56662 EUTPNET 1 2
v6
AS34927 iFog-GmbH 1 1
v6

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.