bgpreport

Network · data from 2026-11-12

AS271415 S3 Net Soluções Inteligentes

Registry name: AS271415 - S3 Net Solucoes Inteligentes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271415, 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.0.48.0/24 No ROA Nonecovered by 179.0.48.0/22 666 99% 67
179.0.50.0/24 No ROA Nonecovered by 179.0.48.0/22 666 99% 67
179.0.51.0/24 No ROA Nonecovered by 179.0.48.0/22 666 99% 67
179.0.49.0/24 No ROA Nonecovered by 179.0.48.0/22 665 99% 67
179.0.48.0/22 No ROA Other IRR onlyRADB, TC 666 99% 67
2804:7b2c::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS271415: AS271415. 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 (AS271415 isn't in the set, or no route object for AS271415 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 objectsAS271415 in itNot covered
AS271415 A single AS number, not a set: AS271415 (this network), 2 route objects.

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: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none179.0.48.0/24No ROA covers it. Add a ROA for AS271415, maxLength 24.666 of 673
Route object: none179.0.48.0/24No route object for it. A route object for 179.0.48.0/22 with origin AS271415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271415 in the RIR database for the space.666 of 673
ROA: none179.0.50.0/24No ROA covers it. Add a ROA for AS271415, maxLength 24.666 of 673
Route object: none179.0.50.0/24No route object for it. A route object for 179.0.48.0/22 with origin AS271415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271415 in the RIR database for the space.666 of 673
ROA: none179.0.51.0/24No ROA covers it. Add a ROA for AS271415, maxLength 24.666 of 673
Route object: none179.0.51.0/24No route object for it. A route object for 179.0.48.0/22 with origin AS271415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271415 in the RIR database for the space.666 of 673
ROA: none179.0.49.0/24No ROA covers it. Add a ROA for AS271415, maxLength 24.665 of 673
Route object: none179.0.49.0/24No route object for it. A route object for 179.0.48.0/22 with origin AS271415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271415 in the RIR database for the space.665 of 673
ROA: none179.0.48.0/22No ROA covers it. Add a ROA for AS271415, maxLength 22.666 of 673
Route object: RIR179.0.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:7b2c::/32No ROA covers it. Add a ROA for AS271415, maxLength 32.634 of 636
Route object: RIR2804:7b2c::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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