bgpreport

Network · data from 2026-11-12

AS268077 Weblink Fibra

Registry name: AS268077 - WEBLINK TECNOLOGIA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268077, 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:57a4:fe40::/42 Invalid: maxLength Nonecovered by 2804:57a4:fe00::/40 11 2%low visibility 6
45.168.169.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
45.168.170.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
45.168.171.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
2804:57a4::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:57a4:fe00::/40 Valid Other IRR onlyRADB 634 100% 69
45.168.168.0/23 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
45.168.168.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
45.168.170.0/23 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
2804:57a4::/33 Valid Other IRR onlyRADB 2 0%low visibility 2
2804:57a4:8000::/33 Valid Other IRR onlyRADB 2 0%low visibility 2
45.168.168.0/22 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS268077: AS268077:AS-WEBLINK-TECNOLOGIA. 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 (AS268077 isn't in the set, or no route object for AS268077 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 objectsAS268077 in itNot covered
AS268077:AS-WEBLINK-TECNOLOGIA TC 1312 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 14 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR11
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:57a4:fe40::/42ROA 2804:57a4:8000::/33 AS268077 has maxLength 33; ROA 2804:57a4::/32 AS268077 has maxLength 32; ROA 2804:57a4:fe00::/40 AS268077 has maxLength 40; the route is a /42. Raise the maxLength, or add a ROA for 2804:57a4:fe40::/42.11 of 636
Route object: none2804:57a4:fe40::/42No route object for it. A route object for 2804:57a4:fe00::/40 with origin AS268077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268077 in the RIR database for the space.11 of 636
Route object: RIR45.168.169.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.168.170.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.168.171.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:57a4::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:57a4:fe00::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR45.168.168.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.168.168.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.168.170.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:57a4::/33Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:57a4:8000::/33Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR45.168.168.0/22Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

38.56.224.0/23RADBNo 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.