bgpreport

Network · data from 2026-11-12

AS16803 Myakka Technologies

Registry name: MYAKKACOMM1 - Myakka Communications, Inc., US · PeeringDB

5IPv4 routes 0.0% RPKI valid · 80.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS16803, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS16803, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

199.47.249.0/24 No ROA Nonecovered by 199.47.248.0/21 673 100% 67
104.244.112.0/21 No ROA RIR databaseARIN 673 100% 67
134.195.28.0/22 No ROA RIR databaseARIN 673 100% 67
199.47.248.0/21 No ROA RIR databaseARIN 673 100% 67
216.133.240.0/21 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS16803's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • ROA: none5
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none199.47.249.0/24No ROA covers it. Add a ROA for AS16803, maxLength 24.673 of 673
Route object: none199.47.249.0/24No route object for it. A route object for 199.47.248.0/21 with origin AS16803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16803 in the RIR database for the space.673 of 673
ROA: none104.244.112.0/21No ROA covers it. Add a ROA for AS16803, maxLength 21.673 of 673
ROA: none134.195.28.0/22No ROA covers it. Add a ROA for AS16803, maxLength 22.673 of 673
ROA: none199.47.248.0/21No ROA covers it. Add a ROA for AS16803, maxLength 21.673 of 673
ROA: none216.133.240.0/21No ROA covers it. Add a ROA for AS16803, maxLength 21.673 of 673

Route objects not announced

Every route object with origin AS16803 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.