bgpreport

Network · data from 2026-11-12

AS271090 STONE NET

Registry name: AS271090 - STONE NET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271090, 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:761c::/33 Invalid: maxLength Nonecovered by 2804:761c::/32 39 6%low visibility 19
2804:761c::/34 Invalid: maxLength Nonecovered by 2804:761c::/32 39 6%low visibility 19
2804:761c:4000::/34 Invalid: maxLength Nonecovered by 2804:761c::/32 39 6%low visibility 19
179.48.146.0/24 Valid Other IRR onlyALTDB 672 100% 66
179.48.147.0/24 Valid Other IRR onlyALTDB 672 100% 66
179.48.144.0/22 Valid Other IRR onlyALTDB, RADB 667 99% 67
179.48.144.0/24 Valid Other IRR onlyALTDB 667 99% 67
179.48.145.0/24 Valid Other IRR onlyALTDB 667 99% 67
179.48.146.0/23 Valid Other IRR onlyALTDB, RADB 667 99% 67
2804:761c::/32 Valid Other IRR onlyALTDB, RADB 634 100% 70
179.48.144.0/23 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3

AS-SET

AS271090's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:761c::/33ROA 2804:761c::/32 AS271090 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:761c::/33.39 of 636
Route object: none2804:761c::/33No route object for it. A route object for 2804:761c::/32 with origin AS271090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271090 in the RIR database for the space.39 of 636
ROA: maxLength2804:761c::/34ROA 2804:761c::/32 AS271090 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:761c::/34.39 of 636
Route object: none2804:761c::/34No route object for it. A route object for 2804:761c::/32 with origin AS271090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271090 in the RIR database for the space.39 of 636
ROA: maxLength2804:761c:4000::/34ROA 2804:761c::/32 AS271090 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:761c:4000::/34.39 of 636
Route object: none2804:761c:4000::/34No route object for it. A route object for 2804:761c::/32 with origin AS271090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271090 in the RIR database for the space.39 of 636
Route object: RIR179.48.146.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.48.147.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.48.144.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.48.144.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.48.145.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.48.146.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:761c::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR179.48.144.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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