Network · data from 2026-11-12
AS274603 FJ TELECOM LTDA
Registry name: AS274603 - FJr Telecom, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274603, 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:90dc::/33 | No ROA | Other IRR onlyALTDB | 634 100% |
| 216.28.192.0/23 | Valid | RIR databaseALTDB, ARIN, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS274603: ALTDB::AS274603:AS-ALL. 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 (AS274603 isn't in the set, or no route object for AS274603 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.
| Name | Database | ASNs | Sets | AS274603 in it | Not covered |
|---|---|---|---|---|---|
| ALTDB::AS274603:AS-ALL | ALTDB1 member set in no database: AS269411:AS-ALL | 1 | 2 | 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 6 are in fix.csv.
- ROA: none1
- Route object: RIR1
- AS-SET: missing member1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:90dc::/33 | No ROA covers it. Add a ROA for AS274603, maxLength 33. |
| Route object: RIR | 2804:90dc::/33 | Route object only in ALTDB. Add it in the RIR database for the space. |
| AS-SET: missing member | ALTDB::AS274603:AS-ALL | AS274603:AS-ALL (ALTDB) lists AS269411:AS-ALL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS274603 whose prefix no peer sees AS274603 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.28.192.0/24 | ALTDB, ARIN | Valid |
| 216.28.193.0/24 | ALTDB, ARIN | Valid |
| 2804:90dc::/32 | RADB | No 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.