bgpreport

Network · data from 2026-11-12

AS271510 AS271510 - D. L. SPOHR & CIA LTDA

Registry name: AS271510 - D. L. SPOHR & CIA LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271510, 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.
179.124.164.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
179.124.164.0/24 Valid Other IRR onlyTC 176 26% 55
179.124.165.0/24 Valid Other IRR onlyTC 176 26% 55
179.124.166.0/24 Valid Other IRR onlyTC 176 26% 55
179.124.167.0/24 Valid Other IRR onlyTC 176 26% 55
179.124.164.0/23 Valid Other IRR onlyTC 114 17% 42
179.124.166.0/23 Valid Other IRR onlyTC 113 17% 42

AS-SET

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

  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR179.124.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR179.124.164.0/24Route object only in TC. Add it in the RIR database for the space.176 of 673
Route object: RIR179.124.165.0/24Route object only in TC. Add it in the RIR database for the space.176 of 673
Route object: RIR179.124.166.0/24Route object only in TC. Add it in the RIR database for the space.176 of 673
Route object: RIR179.124.167.0/24Route object only in TC. Add it in the RIR database for the space.176 of 673
Route object: RIR179.124.164.0/23Route object only in TC. Add it in the RIR database for the space.114 of 673
Route object: RIR179.124.166.0/23Route object only in TC. Add it in the RIR database for the space.113 of 673

Route objects not announced

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

2804:7ca8::/32RADB, TCNo ROA
2804:7ca8::/33TCNo ROA
2804:7ca8:8000::/33TCNo 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.