bgpreport

Network · data from 2026-11-12

AS263629 Brasil TecPar (Allrede/Master)

Registry name: AS263629 - ALLREDE TELECOM MT / BRASIL TECPAR, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263629, 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.
179.125.40.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
138.0.248.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.0.249.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.0.250.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.0.40.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.0.41.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.0.42.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
179.125.41.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
179.125.42.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
179.125.44.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
179.125.45.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
179.125.47.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.0.251.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
170.0.43.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
179.125.46.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
179.125.43.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:104c::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:400::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:800::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:2000::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:2200::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:2a00::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:2c00::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:4200::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:4c00::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:6000::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:6400::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:6800::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:8400::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:8800::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:8c00::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:a800::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:c000::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:e000::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:e200::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:e400::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:ec00::/40 Valid Other IRR onlyRADB, TC 635 100% 69
2804:104c:f800::/40 Valid Other IRR onlyRADB, TC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS263629: AS263629:AS-SET. 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 (AS263629 isn't in the set, or no route object for AS263629 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 objectsAS263629 in itNot covered
AS263629:AS-SET TC 8932,128 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 59 are in fix.csv.

  • Route object: RIR38
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
Route object: RIR179.125.40.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.0.248.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.0.249.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.0.250.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.0.40.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.0.41.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.0.42.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.125.41.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.125.42.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.125.44.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.125.45.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR179.125.47.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.0.251.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.0.43.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR179.125.46.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR179.125.43.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:104c::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:400::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:800::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:2000::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:2200::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:2a00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:2c00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:4200::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:4c00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:6000::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:6400::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:6800::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:8400::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:8800::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:8c00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:a800::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:c000::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:e000::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:e200::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:e400::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:ec00::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:104c:f800::/40Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS263629 whose prefix no peer sees AS263629 announce. Many are kept on purpose (backup routes, space announced only in some places).

138.0.248.0/22RADB, TCValid
138.0.248.0/23RADB, TCValid
138.0.250.0/23TCValid
170.0.40.0/22RADB, TCValid
170.0.40.0/23TCValid
170.0.42.0/23RADB, TCValid
179.125.40.0/21RADB, TCValid
179.125.40.0/22TCValid
179.125.40.0/23TCValid
179.125.42.0/23TCValid
179.125.44.0/22RADB, TCValid
179.125.44.0/23TCValid
179.125.46.0/23TCValid
2804:104c::/32RADB, TCValid
2804:104c:2400::/40RADB, TCValid
2804:104c:2800::/40RADB, TCValid
2804:104c:4400::/40RADB, TCValid
2804:104c:4800::/40RADB, TCValid
2804:104c:a000::/40RADB, TCValid
2804:104c:c800::/40RADB, TCValid
2804:104c:e800::/40RADB, TCValid

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.