AS7048
MHNET TELECOM
AS7048 is MHNET TELECOM (lacnic.net). It announces 10,240 IPv4 addresses in 39 prefixes, and 15 IPv6 prefixes.
Brazil· LACNIC· allocated 2009-04-24· isp
10,240
IPv4 addresses announced
39
IPv4 prefixes
15
IPv6 prefixes
100.00%
of its routes RPKI-valid
0
of its IPv4 geolocated
0
countries
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
None of its IPv4 is geolocated, or it announces only IPv6.
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- MHNET TELECOM
- org
- 05245502000104
- org name
- MHNET TELECOM
- org address
- BR
- org country
- BR
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2009-04-24
- updated
- 2024-06-03
- descr
- MHNET TELECOM
- abuse
- CTIMH
- abuse name
- Centro de tratamento de incidentes MHNET
- abuse email
- abuse@mhnet.com.br
- abuse kind
- role
- admin
- PAC343
- admin name
- Patrick Canton
- admin email
- hostmaster@mhnet.com.br
- admin kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP19draytek0.19%
- 711proxy, geonode, novada0.04%
- None here
- None here
- None here
- None here
- Hosting IP2,30422.50%
- None here
- None here
- None here
- 0.08%
- SMTP IP350.34%
- 0.39%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 186.216.144.0/21 | — | valid | 17 | 2026-10-02 |
| 186.216.144.0/22 | — | valid | 17 | 2026-10-02 |
| 186.216.144.0/23 | — | valid | 17 | 2026-10-02 |
| 186.216.146.0/23 | — | valid | 17 | 2026-10-02 |
| 186.216.148.0/22 | — | valid | 17 | 2026-10-02 |
| 186.216.148.0/23 | — | valid | 17 | 2026-10-02 |
| 186.216.150.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.32.0/20 | — | valid | 17 | 2026-10-02 |
| 187.18.32.0/21 | — | valid | 17 | 2026-10-02 |
| 187.18.32.0/22 | — | valid | 17 | 2026-10-02 |
| 187.18.32.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.34.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.36.0/22 | — | valid | 17 | 2026-10-02 |
| 187.18.36.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.38.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.40.0/21 | — | valid | 17 | 2026-10-02 |
| 187.18.40.0/22 | — | valid | 17 | 2026-10-02 |
| 187.18.40.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.42.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.44.0/22 | — | valid | 17 | 2026-10-02 |
| 187.18.44.0/23 | — | valid | 17 | 2026-10-02 |
| 187.18.46.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.224.0/20 | — | valid | 17 | 2026-10-02 |
| 187.49.224.0/21 | — | valid | 17 | 2026-10-02 |
| 187.49.224.0/22 | — | valid | 17 | 2026-10-02 |
| 187.49.224.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.226.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.227.0/24 | — | valid | 17 | 2026-10-02 |
| 187.49.228.0/22 | — | valid | 17 | 2026-10-02 |
| 187.49.228.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.230.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.232.0/21 | — | valid | 17 | 2026-10-02 |
| 187.49.232.0/22 | — | valid | 17 | 2026-10-02 |
| 187.49.232.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.234.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.236.0/22 | — | valid | 17 | 2026-10-02 |
| 187.49.236.0/23 | — | valid | 17 | 2026-10-02 |
| 187.49.236.0/24 | — | valid | 17 | 2026-10-02 |
| 187.49.238.0/23 | — | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2804:6dc::/32 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc::/33 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc::/34 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:2000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:4000::/34 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:4000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:6000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:8000::/33 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:8000::/34 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:8000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:a000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:c000::/34 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:c000::/35 | Brazil | valid | 20 | 2026-10-02 |
| 2804:6dc:e000::/35 | Brazil | valid | 20 | 2026-10-02 |
00 · Evaluate
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.
01 · License
Then license what you use.
Standard, for detection and decisions inside your own product and operations.
Redistribution, when the data ships onward inside what you sell — priced by scope, not by seat.
Annual terms, a named contact, and flexible payment terms — monthly, quarterly or yearly.