Network · data from 2026-11-12
AS268139 NIANET COMERCIO E SERVICOS DE INFORMATICA
Registry name: AS268139 - NIANET COMERCIO E SERVICOS DE INFORMATICA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268139, 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.
| 45.169.220.0/22 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 2804:589c::/32 | No ROA | Other IRR onlyALTDB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS268139: AS-NIANET. 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 (AS268139 isn't in the set, or no route object for AS268139 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 | AS268139 in it | Not covered |
|---|---|---|---|---|---|
| AS-NIANET | RIPElists itself further down14 member sets in no database: AS-ATHENA, AS-BINERO, AS-COMACE, AS-DKUUG, AS-HOSTERSAS … | 1,848 | 485 | No | 2 |
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 21 are in fix.csv.
- ROA: none2
- Route object: RIR2
- AS-SET: own ASN1
- AS-SET: missing member14
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.169.220.0/22 | No ROA covers it. Add a ROA for AS268139, maxLength 22. |
| Route object: RIR | 45.169.220.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:589c::/32 | No ROA covers it. Add a ROA for AS268139, maxLength 32. |
| Route object: RIR | 2804:589c::/32 | Route object only in ALTDB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-NIANET | AS268139 isn't in AS-NIANET (RIPE) once expanded. Add AS268139 to it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-ATHENA; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-BINERO; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-COMACE; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-DKUUG; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-HOSTERSAS; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-HOSTNORDIC; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-HOUSINGCENTER; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-ITRELATION; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS-TDCH; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS204829:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS207564:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS209186:AS-DOWNSTREAM; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS209861:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-NIANET | AS-NIANET (RIPE) lists AS213733:AS-HACK-FO; no IRR database read has it. |
Route objects not announced
Route objects with origin AS268139 whose prefix no peer sees AS268139 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.169.220.0/23 | RADB | No ROA |
| 45.169.222.0/23 | 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.