bgpreport

Network · data from 2026-11-12

AS21803 Ting Fiber (Cedar Networks)

Registry name: CEDAR-NETWORKS - Cedar Networks, US · PeeringDB

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

Announced routes

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

209.140.0.0/24 Valid Nonecovered by 209.140.0.0/20 672 100% 67
67.223.163.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.167.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.170.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.171.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.174.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.175.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.3.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.13.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.21.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.22.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.25.0/24 Valid Other IRR onlyRADB 672 100% 67
69.39.31.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.2.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.4.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.5.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.12.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.13.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.14.0/24 Valid Other IRR onlyRADB 672 100% 67
209.140.15.0/24 Valid Other IRR onlyRADB 672 100% 67
67.223.160.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.161.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.162.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.164.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.165.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.168.0/24 Valid Other IRR onlyRADB 671 100% 68
67.223.169.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.0.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.1.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.2.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.4.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.5.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.6.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.7.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.8.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.9.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.10.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.14.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.15.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.16.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.19.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.23.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.24.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.26.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.28.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.29.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.30.0/24 Valid Other IRR onlyRADB 671 100% 68
209.140.7.0/24 Valid Other IRR onlyRADB 671 100% 68
209.140.8.0/24 Valid Other IRR onlyRADB 671 100% 68
209.140.9.0/24 Valid Other IRR onlyRADB 671 100% 68
209.140.11.0/24 Valid Other IRR onlyRADB 671 100% 68
69.39.27.0/24 Valid Other IRR onlyRADB 2 0%low visibility 3

AS-SET

AS21803'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 67 are in fix.csv.

  • Route object: none1
  • Route object: RIR51
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none209.140.0.0/24No route object for it. A route object for 209.140.0.0/20 with origin AS21803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21803 in the RIR database for the space.672 of 673
Route object: RIR67.223.163.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.167.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.170.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.171.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.175.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.25.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR69.39.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.2.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.12.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR209.140.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR67.223.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.161.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.162.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.164.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.165.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.168.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR67.223.169.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.2.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.4.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.5.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.6.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.7.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.9.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.10.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.14.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.15.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.16.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.19.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.23.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.24.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.26.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.28.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.29.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.30.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.140.7.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.140.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.140.9.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.140.11.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.39.27.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

67.223.160.0/20RADBValid
67.223.166.0/24RADBValid
67.223.172.0/24RADBValid
67.223.173.0/24RADBValid
69.39.0.0/19RADBValid
69.39.11.0/24RADBValid
69.39.12.0/24RADBValid
69.39.17.0/24RADBValid
69.39.18.0/24RADBValid
69.39.20.0/24RADBValid
98.124.208.0/22RADBValid
209.140.0.0/20RADBValid
209.140.1.0/24RADBValid
209.140.6.0/24RADBValid
209.140.10.0/24RADBValid

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.