bgpreport

Network · data from 2026-11-12

AS28352 Netspeed Brazil

Registry name: AS28352 - NETSPEED LTDA, BR · PeeringDB

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

Announced routes

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

187.0.48.0/20 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.48.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.48.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.52.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.56.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.56.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
187.0.60.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
189.51.192.0/20 Valid Other IRR onlyRADB, TC 669 99% 67
189.51.192.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
189.51.192.0/22 Valid Other IRR onlyTC 669 99% 67
189.51.196.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
189.51.200.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
189.51.200.0/22 Valid Other IRR onlyTC 669 99% 67
189.51.204.0/22 Valid Other IRR onlyTC 669 99% 67
2804:ae0::/32 Valid Other IRR onlyRADB, TC 636 100% 67
187.0.48.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.52.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.54.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.56.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.58.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.60.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
187.0.62.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
189.51.194.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
189.51.198.0/23 Valid Other IRR onlyTC 105 16% 39
189.51.200.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
189.51.202.0/23 Valid Other IRR onlyTC 105 16% 39
189.51.204.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
189.51.206.0/23 Valid Other IRR onlyRADB, TC 105 16% 39
189.51.192.0/23 Valid Other IRR onlyRADB, TC 104 15% 39
189.51.196.0/23 Valid Other IRR onlyTC 104 15% 39
2804:ae0::/33 Valid Other IRR onlyTC 90 14% 38
2804:ae0:8000::/33 Valid Other IRR onlyTC 90 14% 38
189.51.207.0/24 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS28352: AS-NETSPEED. 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 (AS28352 isn't in the set, or no route object for AS28352 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 objectsAS28352 in itNot covered
AS-NETSPEED TC 93345 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 79 are in fix.csv.

  • Route object: RIR33
  • Route object: not announced46
ChangePrefix or setDetailFull-table peers
Route object: RIR187.0.48.0/20Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.48.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.52.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.56.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.0.60.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.192.0/20Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.192.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.192.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.196.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.200.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.200.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR189.51.204.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:ae0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR187.0.48.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.52.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.54.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.56.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.58.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.60.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR187.0.62.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.194.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.198.0/23Route object only in TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.200.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.202.0/23Route object only in TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.204.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.206.0/23Route object only in RADB, TC. Add it in the RIR database for the space.105 of 673
Route object: RIR189.51.192.0/23Route object only in RADB, TC. Add it in the RIR database for the space.104 of 673
Route object: RIR189.51.196.0/23Route object only in TC. Add it in the RIR database for the space.104 of 673
Route object: RIR2804:ae0::/33Route object only in TC. Add it in the RIR database for the space.90 of 636
Route object: RIR2804:ae0:8000::/33Route object only in TC. Add it in the RIR database for the space.90 of 636
Route object: RIR189.51.207.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

187.0.48.0/24RADB, TCValid
187.0.49.0/24RADB, TCValid
187.0.50.0/23RADB, TCValid
187.0.50.0/24RADB, TCValid
187.0.51.0/24RADB, TCValid
187.0.52.0/24TCValid
187.0.53.0/24TCValid
187.0.54.0/24TCValid
187.0.55.0/24TCValid
187.0.56.0/24TCValid
187.0.57.0/24TCValid
187.0.58.0/24TCValid
187.0.59.0/24TCValid
187.0.60.0/24TCValid
187.0.61.0/24TCValid
187.0.62.0/24TCValid
187.0.63.0/24TCValid
189.51.192.0/24TCValid
189.51.193.0/24TCValid
189.51.194.0/24TCValid
189.51.195.0/24TCValid
189.51.196.0/24TCValid
189.51.197.0/24RADB, TCValid
189.51.198.0/24TCValid
189.51.199.0/24RADB, TCValid
189.51.200.0/24TCValid
189.51.201.0/24TCValid
189.51.202.0/24TCValid
189.51.203.0/24RADB, TCValid
189.51.204.0/24TCValid
189.51.205.0/24TCValid
189.51.206.0/24TCValid
2804:ae0::/34TCValid
2804:ae0::/44TCValid
2804:ae0:2600::/40TCValid
2804:ae0:2a00::/40TCValid
2804:ae0:2c00::/40TCValid
2804:ae0:4000::/34TCValid
2804:ae0:4000::/40TCValid
2804:ae0:4400::/40TCValid
2804:ae0:4800::/40TCValid
2804:ae0:8000::/34TCValid
2804:ae0:8200::/40TCValid
2804:ae0:8400::/40TCValid
2804:ae0:8600::/40TCValid
2804:ae0:c000::/34TCValid

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.