Network · data from 2026-11-12
AS61624 ISP SHIELD
Registry name: AS61624 - INFNOC TECNOLOGIA LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61624, 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:945c::/32 | No ROA | Other IRR onlyALTDB, TC | 633 100% |
| 2804:945c:6::/48 | No ROA | Other IRR onlyALTDB | 633 100% |
| 2804:945c:12::/48 | No ROA | Other IRR onlyALTDB | 633 100% |
| 2804:945c:1000::/48 | No ROA | Other IRR onlyALTDB | 633 100% |
| 151.242.95.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS61624: AS-ISPSHIELD. 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 (AS61624 isn't in the set, or no route object for AS61624 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 | AS61624 in it | Not covered |
|---|---|---|---|---|---|
| AS-ISPSHIELD | ALTDB1 member set in no database: AS273876:AS-CUSTOMERS | 82 | 19 | 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 14 are in fix.csv.
- ROA: none4
- Route object: RIR4
- AS-SET: missing member1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:945c::/32 | No ROA covers it. Add a ROA for AS61624, maxLength 32. |
| Route object: RIR | 2804:945c::/32 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:945c:6::/48 | No ROA covers it. Add a ROA for AS61624, maxLength 48. |
| Route object: RIR | 2804:945c:6::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2804:945c:12::/48 | No ROA covers it. Add a ROA for AS61624, maxLength 48. |
| Route object: RIR | 2804:945c:12::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2804:945c:1000::/48 | No ROA covers it. Add a ROA for AS61624, maxLength 48. |
| Route object: RIR | 2804:945c:1000::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-ISPSHIELD | AS-ISPSHIELD (ALTDB) lists AS273876:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS61624 whose prefix no peer sees AS61624 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:945c::/33 | ALTDB | No ROA |
| 2804:945c:1001::/48 | ALTDB | No ROA |
| 2804:945c:1002::/48 | ALTDB | No ROA |
| 2804:945c:1003::/48 | ALTDB | No ROA |
| 2804:945c:8000::/33 | ALTDB | 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.