bgpreport

Network · data from 2026-11-12

AS266471 Silva Oliveira Serviços de Informatica

Registry name: AS266471 - Silva Oliveira Servicos de Informatica Ltda, BR · PeeringDB

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

Announced routes

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

170.83.50.0/24 Invalid: maxLength Nonecovered by 170.83.48.0/22 28 4%low visibility 15
170.83.48.0/22 Valid Other IRR onlyALTDB 671 100% 67
2804:3858::/32 Valid Other IRR onlyALTDB, RADB 634 100% 69
2804:3858:4000::/34 Valid Other IRR onlyALTDB 347 55% 65
2804:3858:8000::/34 Valid Other IRR onlyALTDB 347 55% 65
2804:3858:c000::/34 Valid Other IRR onlyALTDB 347 55% 65
170.83.48.0/23 Valid Other IRR onlyALTDB 202 30% 56
170.83.49.0/24 Valid Other IRR onlyALTDB 201 30% 56
170.83.51.0/24 Valid Other IRR onlyALTDB, RADB 201 30% 56
170.83.48.0/24 Valid Other IRR onlyALTDB 200 30% 56

AS-SET

PeeringDB's irr_as_set for AS266471: AS-266471. 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 (AS266471 isn't in the set, or no route object for AS266471 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 objectsAS266471 in itNot covered
AS-266471 ALTDB 6239 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 12 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength170.83.50.0/24ROA 170.83.48.0/22 AS266471 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 170.83.50.0/24.28 of 673
Route object: none170.83.50.0/24No route object for it. A route object for 170.83.48.0/22 with origin AS266471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266471 in the RIR database for the space.28 of 673
Route object: RIR170.83.48.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3858::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3858:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:3858:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:3858:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.347 of 636
Route object: RIR170.83.48.0/23Route object only in ALTDB. Add it in the RIR database for the space.202 of 673
Route object: RIR170.83.49.0/24Route object only in ALTDB. Add it in the RIR database for the space.201 of 673
Route object: RIR170.83.51.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR170.83.48.0/24Route object only in ALTDB. Add it in the RIR database for the space.200 of 673

Route objects not announced

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

2804:3858::/34ALTDBInvalid: maxLength

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.