AS50763 MCKAYCOM Robert McKay
🇮🇲Org handle: ORG-RM272-RIPE
MCKAYCOM Wireless
RIPE NCCallocated
Announced Prefixes (BGP)
15total
9 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)6,912
Announced (BGP)6,144
IPv6 Addresses
Allocated (RIR)7.9×10²⁹
Announced (BGP)1.5×10²⁹
Routing hygiene
Score 57/100 · High riskRPKI ROA coverage
13.3%
1 prefix RPKI invalid
IRR route objects
93.3%
1 prefix registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
5
diversity 70/100
- 87% of announced prefixes (13 of 15) have no valid ROA, 1 of them RPKI invalid
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
Based on 15 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)15|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-26 | |
| No ROA | Other IRRRIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | Other IRRRIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | Other IRRRIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | Other IRR | 2026-10-26 | |
| No ROA | Other IRRRIPE | 2026-10-26 | |
| Valid | ARINOther IRR | 2026-10-26 |
1-10 of 15
1 / 2
Allocated Prefixes
(RIR)14Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.1.88.0/21 | 🇮🇲 IM | RIPENCC | allocated |
| 185.128.248.0/22 | 🇮🇲 IM | RIPENCC | allocated |
| 185.128.248.0/23 | 🇮🇲 IM | RIPE | assigned |
| 185.128.250.0/24 | 🇮🇲 IM | RIPE | assigned |
| 185.128.251.0/24 | 🇧🇷 BR | RIPE | assigned |
| 185.241.44.0/22 | 🇮🇲 IM | RIPENCC | allocated |
| 185.241.44.0/23 | 🇬🇧 GB | RIPE | assigned |
| 192.75.207.0/24 | 🇨🇦 CA | ARIN | allocated |
| 193.107.204.0/22 | 🇮🇲 IM | RIPENCC | assigned |
| 2400:54a0:2080::/44 | 🇯🇵 JP | APNIC | assigned |
1-10 of 14
1 / 2
All 15 announced prefixes of AS50763 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS50763 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS50763 passes on: usually its customers.
- AS33309Heliacal Networks2
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 AS50763 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/50763Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50763" | jq