bgpreport

Network · data from 2026-11-12

AS53703 KwiKom Communications

Registry name: KWIKOM - KwiKom Communications, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53703, 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.

2604:c900::/32 No ROA Other IRR onlyRADB 634 100% 69
2604:f600::/32 No ROA Other IRR onlyRADB 634 100% 69
64.254.33.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
198.254.28.0/22 Valid Other origin only 671 100% 67
64.39.192.0/19 Valid Other IRR onlyRADB 670 100% 68
72.2.179.0/24 Valid Other IRR onlyRADB 670 100% 68
158.51.164.0/22 Valid Other IRR onlyRADB 670 100% 68
199.68.220.0/22 Valid Other IRR onlyRADB 670 100% 68
199.83.56.0/22 Valid Other IRR onlyRADB 670 100% 68
199.119.144.0/21 Valid Other IRR onlyRADB 670 100% 68
208.92.168.0/21 Valid Other IRR onlyRADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS53703: AS-KWIKOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS53703 isn't in the set, or no route object for AS53703 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS53703 in itNot covered
AS-KWIKOM RADB 5126 Yes 1

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 26 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2604:c900::/32No ROA covers it. Add a ROA for AS53703, maxLength 32.634 of 636
Route object: RIR2604:c900::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2604:f600::/32No ROA covers it. Add a ROA for AS53703, maxLength 32.634 of 636
Route object: RIR2604:f600::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none64.254.33.0/24No ROA covers it. Add a ROA for AS53703, maxLength 24.2 of 673
Route object: RIR64.254.33.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none198.254.28.0/22Route objects for it name AS46180. Add a route object with origin AS53703 in the RIR database for the space.671 of 673
Route object: RIR64.39.192.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR72.2.179.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR158.51.164.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.68.220.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.83.56.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR199.119.144.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR208.92.168.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS53703 whose prefix no peer sees AS53703 announce. Many are kept on purpose (backup routes, space announced only in some places).

70.169.96.0/19RADBValid
70.169.102.0/24RADBValid
70.169.110.0/24RADBValid
72.214.160.0/19RADBValid
72.214.175.0/24RADBValid
98.188.112.0/23RADBValid
98.190.237.0/24RADBValid
174.76.28.0/23RADBValid
174.78.108.0/23RADBValid
184.180.180.0/24RADBValid
184.191.48.0/23RADBValid
2604:2680::/32RADBNo ROA

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.