BRISANET SERVICOS DE TELECOMUNICACOES S.A
AS28126 is BRISANET SERVICOS DE TELECOMUNICACOES S.A (brisanet.com.br). It announces 83,968 IPv4 addresses in 38 prefixes, and 7 IPv6 prefixes.
Brazil· LACNIC· allocated 2008-12-12· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Brazil16,844 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- BRISANET SERVICOS DE TELECOMUNICACOES S.A
- org
- 04601397000128
- org name
- BRISANET SERVICOS DE TELECOMUNICACOES S.A
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2008-12-12
- updated
- 2025-10-08
- descr
- BRISANET SERVICOS DE TELECOMUNICACOES S.A
- abuse
- NOGBR
- abuse name
- NOC Grupo Brisanet
- abuse kind
- role
- admin
- NOGBR
- admin name
- NOC Grupo Brisanet
- 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 IP1,780watchguard, best_proxy_switcher, draytek2.12%
- Residential Proxy IP33,920novada, geonode, dataimpulse40.40%
- floppydata0.00%
- dataimpulse, floppydata0.63%
- None here
- None here
- Hosting IP52,73662.80%
- None here
- None here
- None here
- SSH IP1750.21%
- SMTP IP3090.37%
- 0.03%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 177.37.128.0/17 | — | valid | 18 | 2026-10-02 |
| 177.37.128.0/19 | — | valid | 18 | 2026-10-02 |
| 177.37.160.0/19 | — | valid | 18 | 2026-10-02 |
| 177.37.172.0/23 | — | valid | 17 | 2026-10-02 |
| 177.37.180.0/23 | — | valid | 17 | 2026-10-02 |
| 177.37.182.0/23 | — | valid | 17 | 2026-10-02 |
| 177.37.192.0/19 | — | valid | 18 | 2026-10-02 |
| 177.37.192.0/20 | — | valid | 4 | 2026-10-02 |
| 177.37.208.0/20 | — | valid | 4 | 2026-10-02 |
| 177.37.224.0/19 | — | valid | 18 | 2026-10-02 |
| 177.37.224.0/20 | — | valid | 4 | 2026-10-02 |
| 177.37.240.0/20 | — | valid | 4 | 2026-10-02 |
| 177.37.248.0/23 | — | valid | 17 | 2026-10-02 |
| 177.154.48.0/21 | — | valid | 18 | 2026-10-02 |
| 177.154.48.0/22 | — | valid | 4 | 2026-10-02 |
| 177.154.52.0/22 | — | valid | 4 | 2026-10-02 |
| 187.19.128.0/17 | — | valid | 18 | 2026-10-02 |
| 187.19.128.0/19 | — | valid | 18 | 2026-10-02 |
| 187.19.128.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.132.0/23 | — | valid | 17 | 2026-10-02 |
| 187.19.144.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.160.0/19 | — | valid | 18 | 2026-10-02 |
| 187.19.160.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.176.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.176.0/23 | — | valid | 17 | 2026-10-02 |
| 187.19.192.0/19 | — | valid | 18 | 2026-10-02 |
| 187.19.192.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.208.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.224.0/19 | — | valid | 18 | 2026-10-02 |
| 187.19.224.0/20 | — | valid | 4 | 2026-10-02 |
| 187.19.230.0/23 | — | valid | 17 | 2026-10-02 |
| 206.42.0.0/18 | Brazil | not found | 18 | 2026-10-02 |
| 206.42.0.0/19 | Brazil | not found | 18 | 2026-10-02 |
| 206.42.22.0/24 | Brazil | not found | 17 | 2026-10-02 |
| 206.42.32.0/19 | Brazil | not found | 18 | 2026-10-02 |
| 206.42.44.0/24 | Brazil | not found | 17 | 2026-10-02 |
| 206.42.53.0/24 | Brazil | not found | 17 | 2026-10-02 |
| 206.42.54.0/24 | Brazil | not found | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2804:29b8::/32 | — | valid | 20 | 2026-10-02 |
| 2804:29b8::/33 | — | valid | 20 | 2026-10-02 |
| 2804:29b8:1000::/36 | — | valid | 2 | 2026-10-02 |
| 2804:29b8:5000::/36 | — | valid | 2 | 2026-10-02 |
| 2804:29b8:5400::/40 | — | valid | 20 | 2026-10-02 |
| 2804:29b8:6000::/36 | — | valid | 2 | 2026-10-02 |
| 2804:29b8:8000::/33 | — | valid | 20 | 2026-10-02 |
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.