Network · data from 2026-11-12
AS274713 AS274713 - SOLUCOES SERVICOS INTERNET EIRELI
Registry name: AS274713 - SOLUCOES SERVICOS INTERNET EIRELI, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274713, 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:9274::/32 | Valid | Other IRR onlyRADB, TC | 631 99% |
| 2804:9274::/33 | Valid | Other IRR onlyTC | 336 53% |
| 2804:9274::/34 | Valid | Other IRR onlyTC | 336 53% |
| 2804:9274:4000::/34 | Valid | Other IRR onlyTC | 336 53% |
| 2804:9274:8000::/33 | Valid | Other IRR onlyTC | 336 53% |
| 2804:9274:8000::/34 | Valid | Other IRR onlyTC | 336 53% |
| 2804:9274:c000::/34 | Valid | Other IRR onlyTC | 336 53% |
AS-SET
AS274713 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 7 are in fix.csv.
- Route object: RIR7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2804:9274::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9274:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS274713 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.