Network · data from 2026-11-12
AS53102 S.I. Teleinformatica (Sitel)
Registry name: AS53102 - S.I. TELECOM. SERVICOS DE TELEFONIA LTDA EPP, BR · PeeringDB
51IPv4 routes
98.0% RPKI valid · 98.0% with a route object
18IPv6 routes
100.0% RPKI valid · 16.7% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
16 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS53102, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS53102, 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.
| 38.210.24.0/24 | Invalid: origin | None | 23 3%low visibility |
| 2804:928:e::/48 | Valid | Nonecovered by 2804:928::/33 | 635 100% |
| 2804:928:9::/48 | Valid | Nonecovered by 2804:928::/33 | 631 99% |
| 2804:928:f::/48 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:10::/48 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:11::/48 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:48::/45 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:50::/45 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:da0::/44 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:db0::/44 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:1700::/40 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:1800::/40 | Valid | Nonecovered by 2804:928::/33 | 349 55% |
| 2804:928:ffff::/48 | Valid | Nonecovered by 2804:928:8000::/33 | 349 55% |
| 2804:928:7::/48 | Valid | Nonecovered by 2804:928::/33 | 348 55% |
| 2804:928:c::/48 | Valid | Nonecovered by 2804:928::/33 | 348 55% |
| 2804:928:a::/48 | Valid | Nonecovered by 2804:928::/33 | 347 55% |
| 186.195.50.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 186.195.48.0/20 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 186.195.48.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.48.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.50.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.51.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.52.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.53.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.54.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 186.195.54.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.55.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.56.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.56.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.57.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.58.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.58.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.59.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.60.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.60.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.61.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.62.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.62.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.63.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.160.0/20 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 187.103.160.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.160.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.161.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.162.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.163.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.164.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.164.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.165.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.166.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.166.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.167.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.103.168.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.168.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.170.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.170.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.171.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.172.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.172.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.174.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.174.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 187.103.175.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 186.195.49.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 186.195.52.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 187.103.162.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 187.103.169.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 187.103.173.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 2804:928::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 631 99% |
| 2804:928::/33 | Valid | Other IRR onlyTC | 349 55% |
| 2804:928:8000::/33 | Valid | Other IRR onlyTC | 349 55% |
AS-SET
PeeringDB's irr_as_set for AS53102: AS53102:AS-GLOBAL. 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 (AS53102 isn't in the set, or no route object for AS53102 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 | AS53102 in it | Not covered |
|---|---|---|---|---|---|
| AS53102:AS-GLOBAL | TC | 49 | 1 | Yes | 1 |
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 72 are in fix.csv.
- ROA: origin1
- Route object: none16
- Route object: RIR53
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.210.24.0/24 | ROAs covering it name AS270405, not AS53102. If AS53102 should announce it, add a ROA for AS53102. |
| Route object: none | 38.210.24.0/24 | No route object for it. Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:e::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:9::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:f::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:10::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:11::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:48::/45 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:50::/45 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:da0::/44 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:db0::/44 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:1700::/40 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:1800::/40 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:ffff::/48 | No route object for it. A route object for 2804:928:8000::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:7::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:c::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: none | 2804:928:a::/48 | No route object for it. A route object for 2804:928::/33 with origin AS53102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53102 in the RIR database for the space. |
| Route object: RIR | 186.195.50.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.48.0/20 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.48.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.48.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.50.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.51.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.52.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.53.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.54.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.54.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.55.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.56.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.56.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.57.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.58.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.58.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.59.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.60.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.60.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.61.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.62.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.62.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.63.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.160.0/20 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.160.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.160.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.161.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.162.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.163.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.164.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.164.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.165.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.166.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.166.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.167.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.168.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.168.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.170.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.170.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.171.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.172.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.172.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.174.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.174.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.175.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.49.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.195.52.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.162.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.169.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.103.173.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:928::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:928::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:928:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53102 whose prefix no peer sees AS53102 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.195.56.0/21 | RADB | Valid |
| 187.103.168.0/21 | 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.