bgpreport

Network · data from 2026-11-12

AS53828 Nitel

Registry name: NITEL - NETWORK INNOVATIONS, LLC, US · PeeringDB

31IPv4 routes 58.1% RPKI valid · 61.3% with a route object
5IPv6 routes 20.0% RPKI valid · 20.0% with a route object
12RPKI invalid 2 origin · 10 maxLength
5No ROA 16 with no route object for this origin
15Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS53828, seen from no peer

Announced routes

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

185.234.216.0/24 Invalid: origin Other origin only 2 0%low visibility 2
206.53.202.0/24 Invalid: origin None 2 0%low visibility 2
64.63.173.0/24 Invalid: maxLength Nonecovered by 64.63.128.0/18 2 0%low visibility 2
74.85.108.0/24 Invalid: maxLength Nonecovered by 74.85.96.0/19 2 0%low visibility 2
144.91.218.0/24 Invalid: maxLength Nonecovered by 144.91.192.0/18 2 0%low visibility 2
144.91.219.0/24 Invalid: maxLength Nonecovered by 144.91.192.0/18 2 0%low visibility 2
216.40.0.0/24 Invalid: maxLength Nonecovered by 216.40.0.0/19 2 0%low visibility 2
216.40.1.0/24 Invalid: maxLength Nonecovered by 216.40.0.0/19 2 0%low visibility 2
2605:a380:100::/40 Invalid: maxLength Nonecovered by 2605:a380::/32 2 0%low visibility 2
2605:a380:200::/40 Invalid: maxLength Nonecovered by 2605:a380::/32 2 0%low visibility 2
2605:a380:403::/48 Invalid: maxLength Nonecovered by 2605:a380::/32 2 0%low visibility 2
2605:a380:2000::/48 Invalid: maxLength Nonecovered by 2605:a380::/32 2 0%low visibility 2
216.152.16.0/24 No ROA None 669 99% 67
198.32.132.0/24 No ROA None 2 0%low visibility 2
204.238.52.0/24 No ROA Other IRR onlyALTDB 668 99% 67
199.15.184.0/22 No ROA RIR databaseARIN 668 99% 67
208.87.104.0/24 No ROA RIR databaseARIN 668 99% 67
96.8.97.0/24 Valid Nonecovered by 96.8.96.0/20 2 0%low visibility 2
96.8.99.0/24 Valid Nonecovered by 96.8.96.0/20 2 0%low visibility 2
45.43.240.0/20 Valid RIR databaseARIN 668 99% 67
45.61.16.0/20 Valid RIR databaseARIN 668 99% 67
64.63.128.0/18 Valid RIR databaseARIN 668 99% 67
64.191.64.0/18 Valid RIR databaseARIN 668 99% 67
64.237.112.0/20 Valid RIR databaseARIN 668 99% 67
74.85.96.0/19 Valid RIR databaseARIN 668 99% 67
96.8.96.0/20 Valid RIR databaseARIN 668 99% 67
104.218.104.0/22 Valid RIR databaseARIN 668 99% 67
104.245.24.0/21 Valid RIR databaseARIN 668 99% 67
142.44.64.0/18 Valid RIR databaseARIN 668 99% 67
144.91.176.0/20 Valid RIR databaseARIN 668 99% 67
144.91.192.0/18 Valid RIR databaseARIN 668 99% 67
172.98.96.0/19 Valid RIR databaseARIN 668 99% 67
207.5.64.0/19 Valid RIR databaseARIN 668 99% 67
207.200.192.0/19 Valid RIR databaseARIN 668 99% 67
216.40.0.0/19 Valid RIR databaseARIN 668 99% 67
2605:a380::/32 Valid RIR databaseARIN 631 99% 70

AS-SET

PeeringDB's irr_as_set for AS53828: AS-NITEL-TRANSIT. 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 (AS53828 isn't in the set, or no route object for AS53828 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 objectsAS53828 in itNot covered
AS-NITEL-TRANSIT ARIN 332136 Yes 4

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

  • ROA: origin2
  • ROA: maxLength10
  • ROA: none5
  • Route object: none16
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin185.234.216.0/24ROAs covering it name AS212136, not AS53828. If AS53828 should announce it, add a ROA for AS53828.2 of 673
Route object: none185.234.216.0/24Route objects for it name AS212136. Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: origin206.53.202.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS53828 should announce it, add a ROA for AS53828.2 of 673
Route object: none206.53.202.0/24No route object for it. Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength64.63.173.0/24ROA 64.63.128.0/18 AS53828 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 64.63.173.0/24.2 of 673
Route object: none64.63.173.0/24No route object for it. A route object for 64.63.128.0/18 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength74.85.108.0/24ROA 74.85.96.0/19 AS53828 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 74.85.108.0/24.2 of 673
Route object: none74.85.108.0/24No route object for it. A route object for 74.85.96.0/19 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength144.91.218.0/24ROA 144.91.192.0/18 AS53828 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 144.91.218.0/24.2 of 673
Route object: none144.91.218.0/24No route object for it. A route object for 144.91.192.0/18 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength144.91.219.0/24ROA 144.91.192.0/18 AS53828 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 144.91.219.0/24.2 of 673
Route object: none144.91.219.0/24No route object for it. A route object for 144.91.192.0/18 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength216.40.0.0/24ROA 216.40.0.0/19 AS53828 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 216.40.0.0/24.2 of 673
Route object: none216.40.0.0/24No route object for it. A route object for 216.40.0.0/19 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength216.40.1.0/24ROA 216.40.0.0/19 AS53828 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 216.40.1.0/24.2 of 673
Route object: none216.40.1.0/24No route object for it. A route object for 216.40.0.0/19 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: maxLength2605:a380:100::/40ROA 2605:a380::/32 AS53828 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2605:a380:100::/40.2 of 636
Route object: none2605:a380:100::/40No route object for it. A route object for 2605:a380::/32 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 636
ROA: maxLength2605:a380:200::/40ROA 2605:a380::/32 AS53828 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2605:a380:200::/40.2 of 636
Route object: none2605:a380:200::/40No route object for it. A route object for 2605:a380::/32 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 636
ROA: maxLength2605:a380:403::/48ROA 2605:a380::/32 AS53828 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2605:a380:403::/48.2 of 636
Route object: none2605:a380:403::/48No route object for it. A route object for 2605:a380::/32 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 636
ROA: maxLength2605:a380:2000::/48ROA 2605:a380::/32 AS53828 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2605:a380:2000::/48.2 of 636
Route object: none2605:a380:2000::/48No route object for it. A route object for 2605:a380::/32 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 636
ROA: none216.152.16.0/24No ROA covers it. Add a ROA for AS53828, maxLength 24.669 of 673
Route object: none216.152.16.0/24No route object for it. Add a route object with origin AS53828 in the RIR database for the space.669 of 673
ROA: none198.32.132.0/24No ROA covers it. Add a ROA for AS53828, maxLength 24.2 of 673
Route object: none198.32.132.0/24No route object for it. Add a route object with origin AS53828 in the RIR database for the space.2 of 673
ROA: none204.238.52.0/24No ROA covers it. Add a ROA for AS53828, maxLength 24.668 of 673
Route object: RIR204.238.52.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none199.15.184.0/22No ROA covers it. Add a ROA for AS53828, maxLength 22.668 of 673
ROA: none208.87.104.0/24No ROA covers it. Add a ROA for AS53828, maxLength 24.668 of 673
Route object: none96.8.97.0/24No route object for it. A route object for 96.8.96.0/20 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673
Route object: none96.8.99.0/24No route object for it. A route object for 96.8.96.0/20 with origin AS53828 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53828 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS53828 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.