SEM FRONTEIRAS TELECOMUNICACOES LTDA
AS266475 is SEM FRONTEIRAS TELECOMUNICACOES LTDA (semfronteiras.net.br). It announces 7,168 IPv4 addresses in 26 prefixes, and 14 IPv6 prefixes.
Brazil· LACNIC· allocated 2017-01-10· 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.
- Brazil7,168 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- SEM FRONTEIRAS TELECOMUNICACOES LTDA
- org
- 11972556000166
- org name
- SEM FRONTEIRAS TELECOMUNICACOES LTDA
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2017-01-10
- updated
- 2025-11-19
- descr
- SEM FRONTEIRAS TELECOMUNICACOES LTDA
- abuse
- MAOLI1589
- abuse name
- Makleysh Oliveira
- abuse kind
- role
- admin
- KEBSO29
- admin name
- Kêmio Benevides de Souza
- 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 IP941.31%
- geonode, dataimpulse, smartproxy11.26%
- None here
- None here
- None here
- None here
- Hosting IP1,79225.00%
- CDN IP10meta0.14%
- None here
- None here
- SSH IP530.74%
- None here
- 0.42%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 38.9.112.0/22 | Brazil | not found | 16 | 2026-10-02 |
| 38.9.112.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.9.113.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.9.114.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.9.115.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.56.72.0/22 | Brazil | not found | 16 | 2026-10-02 |
| 38.56.72.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.56.73.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.56.74.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.56.75.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.48.0/20 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.48.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.50.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.52.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.54.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.56.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.58.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.60.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.60.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.61.0/24 | Brazil | not found | 16 | 2026-10-02 |
| 38.191.62.0/23 | Brazil | not found | 16 | 2026-10-02 |
| 170.83.172.0/22 | Brazil | valid | 16 | 2026-10-02 |
| 170.83.172.0/24 | Brazil | valid | 16 | 2026-10-02 |
| 170.83.173.0/24 | Brazil | valid | 16 | 2026-10-02 |
| 170.83.174.0/24 | Brazil | valid | 16 | 2026-10-02 |
| 170.83.175.0/24 | Brazil | valid | 16 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2804:3868::/32 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868::/34 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:200::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:600::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:e00::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:1600::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:1a00::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:4000::/34 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:8000::/34 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:c000::/34 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:f200::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:f400::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:f600::/39 | Brazil | valid | 19 | 2026-10-02 |
| 2804:3868:f800::/39 | Brazil | valid | 19 | 2026-10-02 |
Test the real build first.
An evaluation license puts a full current build in your hands, with no sampling, so you can measure it against your own traffic before anyone talks about terms.