bgpreport

Network · data from 2026-11-12

AS52817 NEWCENTER TELECOM

Registry name: AS52817 - NEWCENTER TELECOM, BR · PeeringDB

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

Announced routes

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

2804:16a8::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:2000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:4000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:6000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:8000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:a000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:c000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
2804:16a8:e000::/35 Valid Nonecovered by 2804:16a8::/32 107 17% 40
170.83.92.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.72.28.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
179.124.204.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
170.83.92.0/23 Valid Other IRR onlyTC 671 100% 67
170.83.94.0/23 Valid Other IRR onlyTC 671 100% 67
177.72.28.0/23 Valid Other IRR onlyTC 671 100% 67
177.72.30.0/23 Valid Other IRR onlyTC 671 100% 67
179.124.204.0/23 Valid Other IRR onlyTC 671 100% 67
179.124.206.0/23 Valid Other IRR onlyTC 671 100% 67
177.72.31.0/24 Valid Other IRR onlyTC 670 100% 67
2804:16a8::/32 Valid Other IRR onlyRADB, TC 634 100% 69
170.83.92.0/24 Valid Other IRR onlyTC 202 30% 54
170.83.93.0/24 Valid Other IRR onlyTC 202 30% 54
170.83.94.0/24 Valid Other IRR onlyTC 202 30% 54
170.83.95.0/24 Valid Other IRR onlyTC 202 30% 54
177.72.28.0/24 Valid Other IRR onlyTC 202 30% 54
177.72.29.0/24 Valid Other IRR onlyTC 202 30% 54
177.72.30.0/24 Valid Other IRR onlyTC 202 30% 54
179.124.204.0/24 Valid Other IRR onlyTC 202 30% 54
179.124.205.0/24 Valid Other IRR onlyTC 202 30% 54
179.124.206.0/24 Valid Other IRR onlyTC 202 30% 54
179.124.207.0/24 Valid Other IRR onlyTC 202 30% 54

AS-SET

PeeringDB's irr_as_set for AS52817: AS52817:AS-ALL. 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 (AS52817 isn't in the set, or no route object for AS52817 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 objectsAS52817 in itNot covered
AS52817:AS-ALL TC 2239 Yes 0

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

  • Route object: none8
  • Route object: RIR22
ChangePrefix or setDetailFull-table peers
Route object: none2804:16a8::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:2000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:4000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:6000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:8000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:a000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:c000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: none2804:16a8:e000::/35No route object for it. A route object for 2804:16a8::/32 with origin AS52817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52817 in the RIR database for the space.107 of 636
Route object: RIR170.83.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.72.28.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR179.124.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.83.92.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.83.94.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.72.28.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.72.30.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.124.204.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.124.206.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.72.31.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:16a8::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR170.83.92.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR170.83.93.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR170.83.94.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR170.83.95.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR177.72.28.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR177.72.29.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR177.72.30.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR179.124.204.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR179.124.205.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR179.124.206.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR179.124.207.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673

Route objects not announced

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