AS6391 URBAN-15-AS - Beanfield Technologies Inc.
π¨π¦ARINassigned
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)6,400
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΈ
Announced (BGP)7.9Γ10Β²βΈ
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARINOther IRR | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 97.107.176.0/20 | π¨π¦ CA | ARIN | allocated |
| 2605:8c80::/32 | π¨π¦ CA | ARIN | allocated |
All 4 announced prefixes of AS6391 β
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS6391 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS6391 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS6391 in the transit part of AS paths: peers, providers or customers.
- AS11831ESecureData2
Transfer History
Registry transfers of AS6391 between organisations.
- AS6391M&A Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS6391 | Urban Networks Inc. | Beanfield Technologies Inc. | M&A |
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 AS6391 should publish an ASPA object
- IPv4 transfers in the ARIN 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/6391Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/6391" | jq