Skip to main content

AS43048

mitigator-cloud

MITIGATOR CLOUD LLC

Registry

Authoritative registration data

AS number
43048
Name
mitigator-cloud
Organisation
MITIGATOR CLOUD LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS43048
109.232.248.0/22 IPv4 /22 not checked
185.6.44.0/22 IPv4 /22 not checked
109.232.248.0/24 IPv4 /24 not checked
109.232.249.0/24 IPv4 /24 not checked
109.232.250.0/24 IPv4 /24 not checked
109.232.251.0/24 IPv4 /24 not checked
91.209.119.0/24 IPv4 /24 not checked
2a02:4f40::/32 IPv6 /32 RPKI not found

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

Source:ripestat:asn-neighbours observed

Observed upstreams

25 networks seen before AS43048 in AS paths

No rows match “”.

Showing – of

Observed downstreams

6 networks seen after AS43048 in AS paths

Observed downstreams
Families
AS207104 BIZONE-AS 414 2,255
v4 v6
AS51464 IBANK2RU 287 1,751
v4
AS206955 EVOTOR-AS 282 1,038
v4
AS201804 NSIS 589 763
v4
AS52016 ADFACT 283 692
v4
AS215259 EVOTOROFD-AS 274 343
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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