bgpreport

Network · data from 2026-11-12

AS263641 TCF Telecom

Registry name: AS263641 - TCF Telecomunicacoes Campo Florido Ltda, BR · PeeringDB

20IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 100.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263641, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263641, 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:1094:1000::/40 Valid Nonecovered by 2804:1094::/32 635 100% 67
2804:1094:1100::/40 Valid Nonecovered by 2804:1094::/32 635 100% 67
2804:1094:2000::/40 Valid Nonecovered by 2804:1094::/32 635 100% 67
2804:1094:2100::/40 Valid Nonecovered by 2804:1094::/32 635 100% 67
2804:1094:d000::/43 Valid Nonecovered by 2804:1094:d000::/36 635 100% 67
2804:7b40::/32 Valid Other origin only 564 89% 67
168.205.60.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
168.205.61.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
179.127.152.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
2804:1094::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:1094:d000::/36 Valid Other IRR onlyRADB 635 100% 67
168.205.60.0/23 Valid Other IRR onlyTC 289 43% 61
168.205.60.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
168.205.62.0/23 Valid Other IRR onlyTC 289 43% 61
179.127.152.0/23 Valid Other IRR onlyTC 289 43% 61
179.127.152.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
179.127.153.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
179.127.154.0/23 Valid Other IRR onlyTC 289 43% 61
179.127.154.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
179.127.156.0/23 Valid Other IRR onlyTC 289 43% 61
179.127.156.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
179.127.157.0/24 Valid Other IRR onlyRADB, TC 289 43% 61
179.127.158.0/23 Valid Other IRR onlyTC 289 43% 61
168.205.62.0/24 Valid Other IRR onlyRADB, TC 288 43% 61
168.205.63.0/24 Valid Other IRR onlyRADB, TC 288 43% 61
179.127.155.0/24 Valid Other IRR onlyRADB, TC 288 43% 61
179.127.158.0/24 Valid Other IRR onlyRADB, TC 288 43% 61
179.127.159.0/24 Valid Other IRR onlyRADB, TC 288 43% 61

AS-SET

PeeringDB's irr_as_set for AS263641: AS263641:AS-TCF. 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 (AS263641 isn't in the set, or no route object for AS263641 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.

NameDatabaseASNsSets Route objectsAS263641 in itNot covered
AS263641:AS-TCF TC 5355 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 28 are in fix.csv.

  • Route object: none6
  • Route object: RIR22
ChangePrefix or setDetailFull-table peers
Route object: none2804:1094:1000::/40No route object for it. A route object for 2804:1094::/32 with origin AS263641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263641 in the RIR database for the space.635 of 636
Route object: none2804:1094:1100::/40No route object for it. A route object for 2804:1094::/32 with origin AS263641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263641 in the RIR database for the space.635 of 636
Route object: none2804:1094:2000::/40No route object for it. A route object for 2804:1094::/32 with origin AS263641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263641 in the RIR database for the space.635 of 636
Route object: none2804:1094:2100::/40No route object for it. A route object for 2804:1094::/32 with origin AS263641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263641 in the RIR database for the space.635 of 636
Route object: none2804:1094:d000::/43No route object for it. A route object for 2804:1094:d000::/36 with origin AS263641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263641 in the RIR database for the space.635 of 636
Route object: none2804:7b40::/32Route objects for it name AS271420. Add a route object with origin AS263641 in the RIR database for the space.564 of 636
Route object: RIR168.205.60.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.205.61.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR179.127.152.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:1094::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1094:d000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR168.205.60.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR168.205.60.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR168.205.62.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.152.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.152.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.153.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.154.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.154.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.156.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.156.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.157.0/24Route object only in RADB, TC. Add it in the RIR database for the space.289 of 673
Route object: RIR179.127.158.0/23Route object only in TC. Add it in the RIR database for the space.289 of 673
Route object: RIR168.205.62.0/24Route object only in RADB, TC. Add it in the RIR database for the space.288 of 673
Route object: RIR168.205.63.0/24Route object only in RADB, TC. Add it in the RIR database for the space.288 of 673
Route object: RIR179.127.155.0/24Route object only in RADB, TC. Add it in the RIR database for the space.288 of 673
Route object: RIR179.127.158.0/24Route object only in RADB, TC. Add it in the RIR database for the space.288 of 673
Route object: RIR179.127.159.0/24Route object only in RADB, TC. Add it in the RIR database for the space.288 of 673

Route objects not announced

Every route object with origin AS263641 is announced.

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.