Network · data from 2026-11-12
AS263263 STAR SERVICOS DE INTERNET LTDA
Registry name: AS263263 - Star Servicos de Internet LTDA, BR · PeeringDB
28IPv4 routes
100.0% RPKI valid · 50.0% with a route object
5IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
15Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS263263, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS263263, 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.
| 138.122.72.0/24 | Valid | Nonecovered by 138.122.72.0/23 | 4 1%low visibility |
| 138.122.73.0/24 | Valid | Nonecovered by 138.122.72.0/23 | 4 1%low visibility |
| 138.122.74.0/24 | Valid | Nonecovered by 138.122.74.0/23 | 4 1%low visibility |
| 138.122.75.0/24 | Valid | Nonecovered by 138.122.74.0/23 | 4 1%low visibility |
| 170.244.220.0/24 | Valid | Nonecovered by 170.244.220.0/23 | 4 1%low visibility |
| 170.244.221.0/24 | Valid | Nonecovered by 170.244.220.0/23 | 4 1%low visibility |
| 170.244.222.0/24 | Valid | Nonecovered by 170.244.222.0/23 | 4 1%low visibility |
| 200.33.129.0/24 | Valid | Nonecovered by 200.33.128.0/23 | 4 1%low visibility |
| 200.33.130.0/24 | Valid | Nonecovered by 200.33.130.0/23 | 4 1%low visibility |
| 200.33.131.0/24 | Valid | Nonecovered by 200.33.130.0/23 | 4 1%low visibility |
| 200.33.132.0/24 | Valid | Nonecovered by 200.33.132.0/23 | 4 1%low visibility |
| 200.33.133.0/24 | Valid | Nonecovered by 200.33.132.0/23 | 4 1%low visibility |
| 200.33.134.0/24 | Valid | Nonecovered by 200.33.134.0/23 | 4 1%low visibility |
| 200.33.135.0/24 | Valid | Nonecovered by 200.33.134.0/23 | 4 1%low visibility |
| 170.244.220.0/22 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 170.244.220.0/23 | Valid | Other IRR onlyRADB | 666 99% |
| 138.122.72.0/22 | Valid | Other IRR onlyRADB, TC | 665 99% |
| 138.122.72.0/23 | Valid | Other IRR onlyRADB | 665 99% |
| 138.122.74.0/23 | Valid | Other IRR onlyRADB | 665 99% |
| 170.244.222.0/23 | Valid | Other IRR onlyRADB | 665 99% |
| 200.33.128.0/21 | Valid | Other IRR onlyRADB, TC | 664 99% |
| 200.33.128.0/22 | Valid | Other IRR onlyRADB | 664 99% |
| 200.33.128.0/23 | Valid | Other IRR onlyRADB | 664 99% |
| 200.33.130.0/23 | Valid | Other IRR onlyRADB | 664 99% |
| 200.33.132.0/22 | Valid | Other IRR onlyRADB | 664 99% |
| 200.33.132.0/23 | Valid | Other IRR onlyRADB | 664 99% |
| 200.33.134.0/23 | Valid | Other IRR onlyRADB | 664 99% |
| 2804:1814:4000::/34 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:1814:8000::/34 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:1814::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:1814::/33 | Valid | Other IRR onlyRADB | 631 99% |
| 2804:1814:8000::/33 | Valid | Other IRR onlyRADB | 631 99% |
| 170.244.223.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS263263: AS263263. 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 (AS263263 isn't in the set, or no route object for AS263263 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 | AS263263 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS263263 | A single AS number, not a set: AS263263 (this network), 20 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 34 are in fix.csv.
- Route object: none14
- Route object: RIR19
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 138.122.72.0/24 | No route object for it. A route object for 138.122.72.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 138.122.73.0/24 | No route object for it. A route object for 138.122.72.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 138.122.74.0/24 | No route object for it. A route object for 138.122.74.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 138.122.75.0/24 | No route object for it. A route object for 138.122.74.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 170.244.220.0/24 | No route object for it. A route object for 170.244.220.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 170.244.221.0/24 | No route object for it. A route object for 170.244.220.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 170.244.222.0/24 | No route object for it. A route object for 170.244.222.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.129.0/24 | No route object for it. A route object for 200.33.128.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.130.0/24 | No route object for it. A route object for 200.33.130.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.131.0/24 | No route object for it. A route object for 200.33.130.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.132.0/24 | No route object for it. A route object for 200.33.132.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.133.0/24 | No route object for it. A route object for 200.33.132.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.134.0/24 | No route object for it. A route object for 200.33.134.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: none | 200.33.135.0/24 | No route object for it. A route object for 200.33.134.0/23 with origin AS263263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263263 in the RIR database for the space. |
| Route object: RIR | 170.244.220.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.244.220.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.72.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.72.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.74.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.244.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.128.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.128.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.128.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.130.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.132.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.33.134.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1814:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1814:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1814::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1814::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1814:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.244.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263263 whose prefix no peer sees AS263263 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:1814::/34 | RADB | Valid |
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.