AS201667 BreadCloud ASMBP LLC
🇺🇸Org handle: ORG-AL1065-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
9total
6 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)3.6×10²⁴
Announced (BGP)3.6×10²⁴
Routing hygiene
Score 28/100 · Medium riskRPKI ROA coverage
77.8%
2 prefixes RPKI invalid
IRR route objects
55.6%
2 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 22% of announced prefixes (2 of 9) have no valid ROA, 2 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 44% of announced prefixes (4 of 9) have no IRR route object for this ASN
Based on 9 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)9|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARINOther IRR | 2026-10-26 | |
82.41.180.0/24MOAS | Invalid | - | 2026-10-26 |
87.76.190.0/24MOAS | Valid | Other IRRRIPE | 2026-10-26 |
| Valid | Other IRRRIPE | 2026-10-26 | |
178.83.66.0/24MOAS | Invalid | - | 2026-10-26 |
178.214.214.0/24MOAS | Valid | Other IRRRIPE | 2026-10-26 |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 82.41.180.0/24 | 🇸🇬 SG | RIPE | assigned |
| 143.20.196.0/24 | 🇺🇸 US | RIPE | assigned |
| 178.83.66.0/24 | 🇺🇸 US | RIPE | assigned |
| 2a06:9801:1e::/48 | 🇺🇸 US | RIPE | assigned |
| 2a06:9801:c5::/48 | 🇬🇧 GB | RIPE | assigned |
| 2a13:9500:15f::/48 | 🇺🇸 US | RIPE | assigned |
All 9 announced prefixes of AS201667 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201667 hands its own prefixes to: transit providers, or peers at an exchange.
- AS137409GSL Networks Pty9
ASPA
No ASPA
Abuse Contact
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 AS201667 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/201667Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201667" | jq