AS264209 LINKFORT TELECOM LTDA ME
🇧🇷Org handle: 234671
LACNICallocated
Announced Prefixes (BGP)
17total
13 IPv44 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)5,120
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)1.6×10²⁹
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
138.97.220.0/22MOAS | No ROA | Other IRR | - |
| No ROA | Other IRR | - | |
| No ROA | Other IRR | - | |
189.51.91.0/24MOAS | No ROA | - | - |
189.51.92.0/23MOAS | No ROA | - | - |
189.51.94.0/23MOAS | No ROA | - | - |
| No ROA | - | - | |
| No ROA | - | - | |
| No ROA | - | - | |
| No ROA | - | - |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 138.97.220.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:2438::/32 | 🇧🇷 BR | LACNIC | allocated |
All 17 announced prefixes of AS264209 →
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS264209 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS264209 passes on: usually its customers.
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS264209 should publish an ASPA object
- IPv4 transfers in the LACNIC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/264209Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/264209" | jq