bgpreport

Network · data from 2026-11-12

AS53713 NATIONAL-CEMENT - National Cement Company

Registry name: NATIONAL-CEMENT - National Cement Company, US · not in PeeringDB

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

Announced routes

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

65.19.169.112/28 Invalid: origin None 19 3%low visibility 17
72.52.83.88/29 Invalid: origin None 19 3%low visibility 17
199.204.95.0/24 No ROA Other IRR onlyALTDB 673 100% 67
208.255.195.0/24 No ROA Other IRR onlyALTDB 673 100% 67
204.80.191.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 68

AS-SET

AS53713 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin65.19.169.112/28ROAs covering it name AS6939, not AS53713. If AS53713 should announce it, add a ROA for AS53713.19 of 673
Route object: none65.19.169.112/28No route object for it. Add a route object with origin AS53713 in the RIR database for the space.19 of 673
ROA: origin72.52.83.88/29ROAs covering it name AS6939, not AS53713. If AS53713 should announce it, add a ROA for AS53713.19 of 673
Route object: none72.52.83.88/29No route object for it. Add a route object with origin AS53713 in the RIR database for the space.19 of 673
ROA: none199.204.95.0/24No ROA covers it. Add a ROA for AS53713, maxLength 24.673 of 673
Route object: RIR199.204.95.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none208.255.195.0/24No ROA covers it. Add a ROA for AS53713, maxLength 24.673 of 673
Route object: RIR208.255.195.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none204.80.191.0/24No ROA covers it. Add a ROA for AS53713, maxLength 24.671 of 673
Route object: RIR204.80.191.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

74.62.38.0/23ARIN, RADBValid
74.62.38.0/24ARINValid
74.62.39.0/24ARINValid
2001:470:468::/48ARINValid
2001:470:46a::/48ARINValid
2620:34:8000::/48ARINNo 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.