bgpreport

Network · data from 2026-11-12

AS36329 INTRADO - Intrado Life & Safety, Inc.

Registry name: INTRADO - Intrado Life & Safety, Inc., US · not in PeeringDB

19IPv4 routes 73.7% RPKI valid · 63.2% with a route object
9IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 16 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
26Route objects not announced registered with origin AS36329, seen from no peer

Announced routes

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

98.78.74.0/24 No ROA Nonecovered by 98.78.74.0/23 673 100% 67
98.78.80.0/21 No ROA Other IRR onlyNTTCOM 673 100% 67
98.78.89.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
98.78.91.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
199.84.136.0/23 No ROA Other IRR onlyRADB 673 100% 67
155.254.152.0/24 Valid Nonecovered by 155.254.144.0/20 673 100% 67
155.254.153.0/24 Valid Nonecovered by 155.254.144.0/20 673 100% 67
155.254.154.0/24 Valid Nonecovered by 155.254.144.0/20 673 100% 67
208.71.176.0/24 Valid Other origin only 673 100% 67
208.71.177.0/24 Valid Other origin only 673 100% 67
2604:7b00:2019::/48 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:2032::/48 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:2033::/48 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:20f0::/48 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:20f8::/48 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:b010::/44 Valid Nonecovered by 2604:7b00::/32 636 100% 67
2604:7b00:2034::/48 Valid Nonecovered by 2604:7b00::/32 635 100% 68
2604:7b00:2035::/48 Valid Nonecovered by 2604:7b00::/32 635 100% 68
2604:7b00:2036::/48 Valid Nonecovered by 2604:7b00::/32 635 100% 68
208.71.179.0/24 Valid Other origin only 625 93% 67
64.58.48.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.49.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.50.0/23 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.51.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.53.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.57.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.62.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
64.58.63.0/24 Valid Other IRR onlyNTTCOM 673 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none16
  • Route object: RIR12
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none98.78.74.0/24No ROA covers it. Add a ROA for AS36329, maxLength 24.673 of 673
Route object: none98.78.74.0/24No route object for it. A route object for 98.78.74.0/23 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.673 of 673
ROA: none98.78.80.0/21No ROA covers it. Add a ROA for AS36329, maxLength 21.673 of 673
Route object: RIR98.78.80.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none98.78.89.0/24No ROA covers it. Add a ROA for AS36329, maxLength 24.673 of 673
Route object: RIR98.78.89.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none98.78.91.0/24No ROA covers it. Add a ROA for AS36329, maxLength 24.673 of 673
Route object: RIR98.78.91.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none199.84.136.0/23No ROA covers it. Add a ROA for AS36329, maxLength 23.673 of 673
Route object: RIR199.84.136.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none155.254.152.0/24No route object for it. A route object for 155.254.144.0/20 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.673 of 673
Route object: none155.254.153.0/24No route object for it. A route object for 155.254.144.0/20 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.673 of 673
Route object: none155.254.154.0/24No route object for it. A route object for 155.254.144.0/20 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.673 of 673
Route object: none208.71.176.0/24Route objects for it name AS11702. Add a route object with origin AS36329 in the RIR database for the space.673 of 673
Route object: none208.71.177.0/24Route objects for it name AS11626. Add a route object with origin AS36329 in the RIR database for the space.673 of 673
Route object: none2604:7b00:2019::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:2032::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:2033::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:20f0::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:20f8::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:b010::/44No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.636 of 636
Route object: none2604:7b00:2034::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.635 of 636
Route object: none2604:7b00:2035::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.635 of 636
Route object: none2604:7b00:2036::/48No route object for it. A route object for 2604:7b00::/32 with origin AS36329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36329 in the RIR database for the space.635 of 636
Route object: none208.71.179.0/24Route objects for it name AS11626. Add a route object with origin AS36329 in the RIR database for the space.625 of 673
Route object: RIR64.58.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.49.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.50.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.51.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.53.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.57.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.62.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR64.58.63.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

64.58.48.0/20NTTCOMValid
64.58.50.0/24NTTCOMValid
64.58.52.0/23NTTCOMValid
64.58.52.0/24NTTCOMValid
64.58.54.0/24NTTCOMValid
64.58.55.0/24NTTCOMValid
64.58.56.0/24NTTCOMValid
64.58.58.0/24NTTCOMValid
64.58.59.0/24NTTCOMValid
64.58.60.0/24NTTCOMValid
64.58.61.0/24NTTCOMValid
98.78.74.0/23ARINNo ROA
98.78.80.0/24NTTCOMNo ROA
98.78.81.0/24NTTCOMNo ROA
98.78.82.0/24NTTCOMNo ROA
98.78.83.0/24NTTCOMNo ROA
98.78.84.0/24NTTCOMNo ROA
98.78.85.0/24NTTCOMNo ROA
98.78.86.0/24NTTCOMNo ROA
98.78.87.0/24NTTCOMNo ROA
98.78.88.0/22NTTCOMNo ROA
98.78.88.0/24NTTCOMNo ROA
98.78.90.0/24NTTCOMNo ROA
155.254.144.0/20ARINValid
199.36.164.0/22ARINValid
2604:7b00::/32ARINValid

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.